Zammad HAProxy Config

[anon77298020]

Infos:

• Used Zammad version: 3.3
• Used Zammad installation source: (source, package, …) package
• Operating system: Debian 10
• Browser + version: Chrome

Expected behavior:

• Login page to display

Actual behavior:

• ERR_CONNECTION_REFUSED

Steps to reproduce the behavior:

• Attempt to navigate to the Zammad site (running nginx) behind HAProxy configured with a https frontend pointing to a http backend (port 3000) results in the above error in Chrome.

Which settings are people using to point to a http backend with HAproxy and Zammad? If I check HAProxy stats it shows the backend as ‘down’ with a layer 4 connection problem - connection refused.

Here’s my HAproxy config:-

HTTPS Frontend:

acl helpdesk-acl var(txn.txnhost) -m str -i ticket.somedomain.com
use_backend helpdesk_ipvANY if helpdesk-acl

HTTP Backend:

backend helpdesk_ipvANY
mode http
id 104
log global
http-response set-header Strict-Transport-Security max-age=31536000;
timeout connect 30000
timeout server 30000
retries 3
option httpchk GET /
server server 192.168.5.184:3000 id 122 check inter 1000

Nginx configuration unchanged apart from adding my external FQDN.

Many thanks

[MrGeneration]

Sounds like you’re trying to access port 3000 from outside of the machine which will not work by default.
The main reason for this is that puma listens on port 3000 on localhost (ipv4).

This part of our documentation should help you:
https://docs.zammad.org/en/latest/appendix/configure-env-vars.html

[anon77298020]

Many thanks for the reply - I had a blonde moment and hadn’t specified the certificate on my HTTPS frontend… Doh!

All working now.