Error in frontend: Something happened and the Taiga has captured

Troubleshooting Self hosted Taiga
1

Installed Taiga using Docker in a Windows 10 machine.

All working fine on current machine, changed .env file TAIGA_DOMAIN=xxx.xxx.xxx.xxx:9000 to reflect the IP of the host machine.

Taiga is reachable from browser in host machine.

When trying to access Taiga at xxx.xxx.xxx.xxx:9000 from another machine in the same network, I get error in frontend

Something happened and the Taiga has captured the error to be able to work on it.

image
image1920×737 100 KB

2

can you share your nginx config?

3

Sure, and thanks for your answer.

Is it on the taiga.conf file?. I have not really touched anything on that file, looks like this:

server {
    listen 80 default_server;

    client_max_body_size 100M;
    charset utf-8;

    # Frontend
    location / {
        proxy_pass http://taiga-front/;
        proxy_pass_header Server;
        proxy_set_header Host $http_host;
        proxy_redirect off;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme $scheme;
    }

    # API
    location /api/ {
        proxy_pass http://taiga-back:8000/api/;
        proxy_pass_header Server;
        proxy_set_header Host $http_host;
        proxy_redirect off;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme $scheme;
    }

    # Admin
    location /admin/ {
        proxy_pass http://taiga-back:8000/admin/;
        proxy_pass_header Server;
        proxy_set_header Host $http_host;
        proxy_redirect off;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme $scheme;
    }

    # Static
    location /static/ {
        alias /taiga/static/;
    }

    # Media
    location /_protected/ {
        internal;
        alias /taiga/media/;
        add_header Content-disposition "attachment";
    }

    # Unprotected section
    location /media/exports/ {
        alias /taiga/media/exports/;
        add_header Content-disposition "attachment";
    }

    location /media/ {
        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme $scheme;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass http://taiga-protected:8003/;
        proxy_redirect off;
    }

    # Events
    location /events {
        proxy_pass http://taiga-events:8888/events;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_connect_timeout 7d;
        proxy_send_timeout 7d;
        proxy_read_timeout 7d;
    }
}
4

Hi there!

The error happens because, for the domain, you used localhost instead of the LAN IP Address.

If you connect from another machine, then your browser will search for the API endpoint and the websocket endpoint on localhost.

Hope this clarifies it!

Best regards!

5

Hi Charlie thanks for your answer, but I am not sure if I follow you. I mentioned in my post the above mentioned.

Maybe I am wrong?.

6

Did you recreate the containers afterwards?

Because your dev tools show that it is trying to connect to localhost, that’s why I mentioned localhost.

It should be enough to do docker-compose up -d if you are using the docker-compose method.

Regards!

7

even after recreate, still same error, I can also get conf.json file at xxx.xxx.xxx.xxx:9000/conf.json and shows this:

{
    "api": "http://localhost:9000/api/v1/",
    "eventsUrl": "ws://localhost:9000/events",
    "baseHref": "/",
    "eventsMaxMissedHeartbeats": 5,
    "eventsHeartbeatIntervalTime": 60000,
    "eventsReconnectTryInterval": 10000,
    "debug": false,
    "debugInfo": false,
    "defaultLanguage": "en",
    "themes": ["taiga"],
    "defaultTheme": "taiga",
    "defaultLoginEnabled": true,
    "publicRegisterEnabled": false,
    "feedbackEnabled": true,
    "supportUrl": "https://community.taiga.io/",
    "privacyPolicyUrl": null,
    "termsOfServiceUrl": null,
    "maxUploadFileSize": null,
    "contribPlugins": [],
    "gitHubClientId": "",
    "gitLabClientId": "",
    "gitLabUrl": "",
    "tagManager": { "accountId": null },
    "tribeHost": null,
    "enableAsanaImporter": false,
    "enableGithubImporter": false,
    "enableJiraImporter": false,
    "enableTrelloImporter": false,
    "gravatar": false,
    "rtlLanguages": [
        "ar",
        "fa",
        "he"
    ]
}

Should I manually modify conf.json to remove “localhost”? how to access it?

8

Hi @Pedro_Sanchez_Roca dro,

You just should to follow 30 min setup guide and change TAIGA_DOMAIN with the correct value. Then, you have to restart the services.

Best regards

9

Thanks David, already done that. TAIGA_DOMAIN is at the correct value, superuser created, restart service, etc.

Works in host machine Just not accessible from other machines.

10

Try to force to remove the containers of the services to apply the new change.

docker compose rm taiga-front taiga-back taiga-async taiga-async-rabbitmq taiga-protected taiga-events taiga-events-rabbitmq

And start again taiga to recreate the container again.