Messages

Thanks,

this solved the problem :)

Hi,

after updating to 26.1.3 I have X-Forwarded Header problems with Caddy.

Before the update the headers on a proxy backend looked like this:

Host: domain.xyz.de
X-Forwarded-For: 192.168.10.171, 192.168.100.1
X-Forwarded-Host: domain.xyz.de, domain.xyz.de
X-Forwarded-Proto: https
X-Forwarded-Server: 127.0.1.1

After the update the headers a looking like this:

Host: 192.168.100.150
X-Forwarded-For: 192.168.10.171
X-Forwarded-Host: 192.168.100.150
X-Forwarded-Server: 127.0.1.1

Under Caddy/Reverse Proxy/Headers I didn't configure any custom headers. Under General Settings/Advanced is for Client IP Headers the default X-Forwarded-For selected.

Any idea what broke this or is this a problem with the latest Caddy update?

Can confirm, 1.17.2 solved the problem for me

Hi,

having the same problem since 09.05.2024 with version 1.17.1. Zenarmor crashes after 5-10s again and again. It dosen't matter if i use the native or emulated driver.

While debugging i narrowed it down, that the dns record "cti.zenarmor.com" cloud not be resolved. I'm using AdGuard Home that runs on port 53 on my OPNsense as my main DNS Server. In the log i cloud see, that this domain is not being resolved. When I disabled the Cloud Threat Intelligence it was running with an emulated driver.

Right now I uninstalled Zenarmor, so that my firewall is stable again.

For the last year i never had an problem with my Zenarmor installation using the native driver