how do I troubleshoot this ?

Troubleshooting
1

I used the GitHub - 6Ministers/taiga-io-docker-compose-for-projects: About Fast set-up Taiga Kanban for Business with Docker Compose to setup a host the other day. It didn’t work right out of the box, so I added ngnix as a webserver and somehow got it working.

Today, I am retracing my steps and stumpling around.

I see this error. On the URL. Docker is not showing any errors.

taiga_error
taiga_error1356×979 75.8 KB

I think my error is coming from ngnix. I don’t appear to be able to connect the proxy. Any suggestions ?

I see 426 codes in my ngnix logs.

34.206.159.129 - - [04/Sep/2025:16:09:04 +0000] “GET /events HTTP/1.1” 426 16 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36”
34.206.159.129 - - [04/Sep/2025:16:09:13 +0000] “GET /events HTTP/1.1” 426 16 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36”
34.206.159.129 - - [04/Sep/2025:16:09:21 +0000] “GET /events HTTP/1.1” 426 16 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36”

I have this hosts file.

127.0.0.1 localhost taiga taiga.chesapeakebay.net
#10.128.17.49 taiga.chesapeakebay.net taiga

The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

I have this .env file.

```
Taiga’s URLs - Variables to define where Taiga should be served

TAIGA_SCHEME=http # serve Taiga using “http” or “https” (secured) connection
TAIGA_DOMAIN=taiga.chesapeakebay.net # 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”)

Taiga’s Secret Key - Variable to provide cryptographic signing

SECRET_KEY=“secret” # Please, change it to an unpredictable value!!

Taiga’s Database settings - Variables to create the Taiga database and connect to it

POSTGRES_USER=taiga # user to connect to PostgreSQL
POSTGRES_PASSWORD=taiga # database user’s password

Taiga’s SMTP settings - Variables to send Taiga’s emails to the users

EMAIL_BACKEND=smtp # use an SMTP server or display the emails in the console (either “smtp” or “console”)
EMAIL_HOST=smtp.chesapeakebay.net # SMTP server address
EMAIL_PORT=465 # default SMTP port
EMAIL_HOST_USER=taiga@chesapeakebay.net # user to connect the SMTP server
EMAIL_HOST_PASSWORD= # SMTP user’s password
EMAIL_DEFAULT_FROM=taiga@chesapeakebay.net # default email address for the automated emails

EMAIL_USE_TLS/EMAIL_USE_SSL are mutually exclusive (only set one of those to True)

EMAIL_USE_TLS=False # use TLS (secure) connection with the SMTP server
EMAIL_USE_SSL=True # use implicit TLS (secure) connection with the SMTP server

Taiga’s RabbitMQ settings - Variables to leave messages for the realtime and asynchronous events

RABBITMQ_USER=taiga # user to connect to RabbitMQ
RABBITMQ_PASS=taiga # RabbitMQ user’s password
RABBITMQ_VHOST=taiga # RabbitMQ container name
RABBITMQ_ERLANG_COOKIE=my-cookie # unique value shared by any connected instance of RabbitMQ

Taiga’s Attachments - Variable to define how long the attachments will be accesible

ATTACHMENTS_MAX_AGE=360 # token expiration date (in seconds)

Taiga’s Telemetry - Variable to enable or disable the anonymous telemetry

ENABLE_TELEMETRY=True
``

My ngnix config looks like this.
server {
listen 443 ssl;
#listen [::]:443 default_server;
server_name taiga.chesapeakebay.net;

# SSL Certificate Configuration
ssl_certificate /etc/pki/tls/certs/chesapeakebay_net.crt;
ssl_certificate_key /etc/pki/tls/private/chesapeakebay_net.key;
ssl_trusted_certificate /etc/pki/tls/certs/chesapeakebay_net-ca.crt;  

# Logging
access_log /var/log/nginx/taiga_access.log;
error_log /var/log/nginx/taiga_error.log;

location / {
    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_redirect off;
    proxy_pass http://127.0.0.1:8000/;
}
2

I figured this out. The moderator can delete this one.