502 error after upgrade

Infos:

  • Used Zammad version: 3 upgrade to 4
  • Used Zammad installation type: Package
  • Operating system: debian 9
  • Browser + version: firefox 88

Expected behavior:

  • functional Zammad environment

Actual behavior:

  • Nginx bad gateway 502 error

Steps to reproduce the behavior:

All services are running

/var/log/nginx/zammad.error.log;
021/04/26 12:49:30 [error] 4651#4651: *17 upstream timed out (110: Connection timed out) while connecting to upstream, client: 185.113.87.215, server: domain, request: “GET /ws HTTP/1.1”, upstream: “http://127.0.0.1:6042/ws”, host: “servicedesk.cns-it.nl”
2021/04/26 12:50:51 [error] 628#628: *1 connect() failed (110: Connection timed out) while connecting to upstream, client: 185.113.87.215, server: domain, request: “GET /ws HTTP/1.1”, upstream: “http://127.0.0.1:6042/ws”, host: “domain”
2021/04/26 12:51:27 [error] 628#628: *8 connect() failed (110: Connection timed out) while connecting to Domain/"

Can anyone point me in the right direction?

Looks like Zammad is not listening to it’s ports.

ss -tulpen should show Ports 3000 and 6042 on default installations.

Sometimes PIDs get stuck, you could enforce it to be clean like so:
systemctl stop zammad; rm -rf /opt/zammad/tmp/pids/; systemctl start zammad

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