502 Bad Gateway all the time

  • Used Zammad version: 2.8.x
  • Used Zammad installation source: (source, package, …)
  • Operating system: macOS
  • Browser + version: Chrome

Expected behavior:

no 502

Actual behavior:

502 bad gateway all the time

Steps to reproduce the behavior:

Just open the ticket Sys and wait.

2019/02/05 11:28:16 [error] 13939#0: *29720153 connect() failed (111: Connection refused) while connecting to upstream, client: xx.xx.xx.xx, server: xxx, request: “POST /api/v1/message_receive HTTP/1.1”, upstream: “http://[::1]:3000/api/v1/message_receive”, host: “xxx”, referrer: “https://xxx/

server {
listen 443 ssl http2;
server_name xxx;
ssl on;
ssl_certificate /etc/letsencrypt/live/xxx/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/xxx/privkey.pem;
ssl_session_cache shared:SSL:10m;
ssl_stapling on;
ssl_stapling_verify on;

location /.well-known {
root /projects/letsencrypt/webrootauth;
expires 365d;

location / {
proxy_pass http://localhost:3000/;
proxy_buffering off;
proxy_cache off;
keepalive_timeout 0;

Change localhost to for both upstream servers, the puma-server does not listen to IPv6.

You should be fine then, if not, check your firewall.

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.