Not sure what’s going on, unable to invite new users now via SMTP even though the settings for SMTP are correct. When I make SMTP “console” in the .env file it allows me to add existing users. I tried turning off firewall and same issue. With SMTP enabled it causes an error. In the browser console I get a 502 Bad Gateway nginx/1.19.10 when sending the POST request.
Please see the logs:
taiga-docker-taiga-gateway-1 | 172.18.0.1 - - [05/Mar/2024:18:52:35 +0000] "POST /api/v1/memberships/bulk_create HTTP/1.0" 502 158 "https://taiga.website.com/project/project-name/admin/memberships" "Mozilla/5.0 (Windows NT 10.0; rv:123.0) Gecko/20100101 Firefox/123.0" "198.44.122.31"
taiga-docker-taiga-back-1 | [2024-03-05 18:52:36 +0000] [1] [WARNING] Worker with pid 27 was terminated due to signal 9
taiga-docker-taiga-back-1 | [2024-03-05 18:52:36 +0000] [47] [INFO] Booting worker with pid: 47
This is my host machine nginx conf that is proxy passing to port 9000:
server {
server_name taiga.website.com;
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://localhost:9000/;
}
# Events
location /events {
proxy_pass http://localhost:9000/events;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_connect_timeout 7d;
proxy_send_timeout 7d;
proxy_read_timeout 7d;
}
# TLS: Configure your TLS following the best practices inside your company
# Logs and other configurations
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/taiga.website.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/taiga.website.com/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = taiga.website.com) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name taiga.website.com;
listen 80;
return 404; # managed by Certbot
}
Here’s the latest container info, a docker pull was run just today so everything is up to date.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5fa1525a80d9 nginx:1.19-alpine "/docker-entrypoint.…" 15 minutes ago Up 3 minutes 0.0.0.0:9000->80/tcp, :::9000->80/tcp taiga-docker-taiga-gateway-1
55dfdc5594e4 taigaio/taiga-back:latest "./docker/entrypoint…" 15 minutes ago Up 3 minutes 8000/tcp taiga-docker-taiga-back-1
8cb930d8bf31 taigaio/taiga-back:latest "/taiga-back/docker/…" 15 minutes ago Up 3 minutes 8000/tcp taiga-docker-taiga-async-1
786705e6dc30 postgres:12.3 "docker-entrypoint.s…" 15 minutes ago Up 3 minutes (healthy) 5432/tcp taiga-docker-taiga-db-1
37dc77e12cb8 rabbitmq:3.8-management-alpine "docker-entrypoint.s…" 15 minutes ago Up 3 minutes 4369/tcp, 5671-5672/tcp, 15671-15672/tcp, 15691-15692/tcp, 25672/tcp taiga-docker-taiga-events-rabbitmq-1
39e4902e2189 taigaio/taiga-front:latest "/docker-entrypoint.…" 15 minutes ago Up 3 minutes 80/tcp taiga-docker-taiga-front-1
4fd4fa4f8a98 taigaio/taiga-protected:latest "./docker/entrypoint…" 15 minutes ago Up 3 minutes 8003/tcp taiga-docker-taiga-protected-1
32667475ad79 rabbitmq:3.8-management-alpine "docker-entrypoint.s…" 15 minutes ago Up 3 minutes 4369/tcp, 5671-5672/tcp, 15671-15672/tcp, 15691-15692/tcp, 25672/tcp taiga-docker-taiga-async-rabbitmq-1
Thoughts so far: something is wrong with my nginx conf but not sure what. This may be causing the gunicorn workers to timeout. SMTP for email used to work but stopped.
