- Used Zammad version: .3.0-1714727086.86c0f001.jammy
- Used Zammad installation type: on-premise, NOT Docker!
- Operating system: Ubuntu Server
- Browser + version: Firefox, Safari, Chrome, Edge, …
Expected behavior:
- I expect Zammad to not serve its own certificate and instead use the certificate created on our reverseproxy (nginx) which is hosted on its own machine and IP-Address.
Actual behavior:
- Zammad serves its own certificate, therefore our clients dont trust it.
I suppose it’s a problem with my zammad.conf on the zammad-server.
(it does indeed contain a “listen 443” using its own self-signed certificate)
Question: What zammad.conf do i have to use, so that Zammad does not serve a certificate on its own and just eats up the letsencrypt-certificate from our external ReverseProxy?
Thanks!