Infos:
- Used Zammad version: 6.1.0
- Used Zammad installation type: (source, package, docker-compose, …) package
- Operating system: Centos 7
- Browser + version: Chrome
Expected behavior:
Chat window to be available in my web aplication
Actual behavior:
Get error 502 (Bad Gateway)
Steps to reproduce the behavior:
Hi,
I have an installation of version 6.10 on Centos 7.
The network is as follows:
Internet >>> Apache Proxy >>> NGINX Proxy >>> Zammad
The Zammad installation is with packages and the NGINX Proxy is the default configuration. Zammad listening on localhost only and the N Proxy running in the same machine. This machine hasn’t got an interface on the internet, instead it access the internet through the machine running the Apache proxy and iptables.
The Apache proxy passes packets to the N Proxy as it can’t pass them directly to Zammad as it’s only listening on localhost.
This installation works well for Zammad and has been working for ages.
I’m now trying to start using the chat on an web application I wrote. and I get the 502 bad gateway error.
I looked around and couldn’t see anyone who actually has resolved this issue.
If I try to access the chat from the internal network, using postman it connects OK. I assume this means that the N Proxy is set up OK, but if I try the same thing from the public IP, it faiils with 502.
The certificates are in the A proxy
My questions are:
Is it possible to get my current infrastructure to work and do you have a tutorial for this?
Would it be better to to get Zammad to listen in all interfaces, switch off the N proxy and get the A proxy in the firewall to connect directly to Zammad, and again, is there a special tutorial for that?
Is there any problem with that or do I need to do anything else apart from listening on all interfaces for Zammad to carry on working correctly?
Any other ideas?
Thanks a lot.