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
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?