Zammad and nginx running, but getting 502

Technical assistance
1

Infos:

  • Used Zammad version: I hope latest, can’t access web gui to check and I was unable to find the console way to check
  • Used Zammad installation type: Package
  • Operating system: Ubuntu
  • Browser + version: Chrome Mac OS Latest

Expected behavior:

Zammad runs under nginx with Lets encrypt certificate. The setup was working correctly for multiple months.

Actual behavior:

Accessing the set hostname now shows Nginx Error 502. In its console it shows

2023/10/16 09:35:35 [error] 3282#3282: *349 connect() failed (111: Connection refused) while connecting to upstream, client: 37.188.128.160, server: help.>

Steps to reproduce the behavior:

Just run zammad with nginx for months and one day wake up to not working enviroment :smiley:

The issue is, when I check production log and any other logs, there is no error than the one from nginx. All zammad linux services are reporting as running (active)

This is how zammad logs looks: BCPaste

Do you have any idea, what can cause this issue?

2

Hello,

I am just refreshing the thread as I really need help with this.

Thank you!

3

It looks like at least parts of your isntance are running fine.
By default you should see a process listening on Ports 3000 and 6042 when running ss -tulpen.

If not stop Zammad and start it again.
If this doesn’t help, stop Zammad and run rm -rf /opt/zammad/tmp/pids/. only do this when it’s not running

If this still doesn’t help, restart Zammad and look at the last entries from the moment on your started Zammad. This might help.

4

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