[SOLVED] 502 Bad Gateway from URL on fresh install

Technical assistance
1
  • Used Zammad version: Latest (6.4)
  • Used Zammad installation type: Package
  • Operating system: Ubuntu Server 24.04 LTS
  • Browser + version: All (Mostly Vivaldi Stable, tested in Edge/Chrome)

Expected behavior: Reach landing page when accessing https://www.zammad.mydomain.com.

Actual behavior: 502 Bad Gateway when navigating by domain. Works fine if navigating directly to internal IP.

Steps to reproduce the behavior: Umm. Try to go to the URL? This issue hasn’t been resolved, and it never worked as expected.

Ok, so a bit about my environment. I’m self hosting a few different services, and in My DMZ, I have a dedicated Nginx reverse proxy, along with Zammad and a few other services. I can navigate directly to the servers IP in a browser and get the webpage just fine, but I can’t get there when I hit the URL. The conf on my dedicated RP is correct, but I don’t really understand upstream servers to be honest, so any help is appreciated. The only logs I have from NGINX are just connection refused to upstream server.

2

SO for anyone who’s allergic to reading documentation like me, you HAVE to setup Nginx (or apache, if you hate yourself) on the Zammad server, and then specify your IP address or FQDN in all of the upstream server blocks and any block containing server_name, then on your external reverse proxy, you’ll route all traffic through FQDN/IP:443.

Zammad is pretty sweet, and I’m really glad I’ve found it!

2 Likes