Taiga is down. Events are disabled

Troubleshooting Self hosted Taiga
1

Any ideas on how to resolve the following?

Events are disabled: the maximum number of connection errors has been reached.

I brought down the services with

docker compose -f docker-compose.yml down

then I brought them back up with

./launch-taiga.sh

I am also getting a lot of errors with

Net::ERR_BLOCKED_BY_CLIENT
2

Hi there,

Please try accesing Taiga from a private window. It is quite possible that you have a browser extension blocking the wss requests.

Best regards!

3

G’day Charles

Accessing via a private window gave the same result.

I have also cleared the events rabbit queue in case it was stored externally, stopped the events rabbit queue, removed the container and started again. Still the same errors appear.

4

Any further ideas?

taiga has been dead in the water now for me for close to a month.
I’m going to give it more time to get it working again.

If I can’t get it working I’ll ditch it for something else. Is tenzu workable enough to move to?

5

Hi there,

Please help us help you. Logs? Your config, anonymizing private data? Does it not work in general? Are you running it on a bare metal server? A VM? Do you have a firewall in front of Taiga? Is it all running on localhost?

Please provide as much data as you can.

Best regards!

6

G’day Charlie.

It’s a new style docker installation running on a virtual server.
It was running fine for a couple of months.
From what I see from the rabbitmq logs there are no issues.

The issue is the front end is trying to get to the backend via ws://localhost:9000/events - which is what the nginx conf file handles.
It should be going to https:://sub.domain.tld/events.

How to fix that I’m currently stuck with.
It might have something to do with conf.json

{
    "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"
    ]
}

Might that be the issue?

7

It may very well be!

Try changing the events URL. Still, try with wss:// instead of https://, since events uses websocket technology to sync status across different users.

In any case, I’m not sure if it should not be working just because of that. If events fail, you would not get syncing, but the rest of the app should be working. Also, the API port looks wrong to me.

You are using GitHub - taigaio/taiga-docker instead of an unofficial one, right? Additionally, please look at the included taiga.conf inside the taiga-gateway folder, since the proxy should be handling the upgrade of the WS.

Best!

8

I am using a fork of that repository. GitHub - csmu-cenr/taiga-docker. The fork is up to date with GitHub - taigaio/taiga-docker.

9

It’s the same - and nothing like the conf.json file I posted.
Looks like the conf.json file is mangled somehow.

10

Resolved.

Changed docker-compose.yml to use an external conf.json.

  taiga-front:
    image: taigaio/taiga-front:latest
    environment:
      TAIGA_URL: "${TAIGA_SCHEME}://${TAIGA_DOMAIN}"
      TAIGA_WEBSOCKETS_URL: "${WEBSOCKETS_SCHEME}://${TAIGA_DOMAIN}"
      TAIGA_SUBPATH: "${SUBPATH}"
      # ...your customizations go here
    networks:
      - taiga
    volumes:
      - ./conf.json:/usr/share/nginx/html/conf.json

then changed the conf.json file to

{
    "api": "https://taiga.domain.tld/api/v1/",
    "eventsUrl": "wss://taiga.domain.tld/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"
    ]
}

brought the taiga processes down with

docker compose -f docker-compose.yml down

then restarted

./launch-taiga.sh

Thanks for your support Charlie.

Cheers!

Edit

Had to change the .env file to get attachments working.

# Taiga's URLs - Variables to define where Taiga should be served
TAIGA_SCHEME=https  # serve Taiga using "http" or "https" (secured) connection
TAIGA_DOMAIN=sub.domain.tld  # Taiga's base URL
SUBPATH="" # it'll be appended to the TAIGA_DOMAIN (use either "" or a "/subpath")
WEBSOCKETS_SCHEME=wss  # events connection protocol (use either "ws" or "wss")

Cheers!

11

Yeah, this is a different config file, this is the nginx one, not the taiga-front config. It was so you could check expected hosts, ports, and the like.

12

Amazing to hear!

Though, since the repo is not modified from the official one, it should be enough to change the .env without including the modified conf.json, I think.

Best!

1 Like