Caddy reverse proxy not working after upgrade to 25.7.1_1

Started by allenlook, August 15, 2025, 09:27:54 PM

Previous topic - Next topic
As the topic indicates, I upgraded from 25.4 to 25.7.1_1 and now my Caddy reverse proxies no longer work.

I have three, two of which are directly accessible web pages, and one of which is a service that listens on a port.

All were working fine before the upgrade, but now none of them function properly, and I get an HTTP error 502.

Rebooting the firewall, restarting the Caddy service, and restarting the web servers has not helped.

DNS is working on the firewall and the machines are each accessible by their names on the local network, e.g. SERVER and SERVER.home.arpa.

Any suggestions for further troubleshooting would be greatly appreciated.
Minisforum UN100D, N100, 8GB, 256GB nVME w/ZFS

This morning one of the web pages is responding, so the Caddy service and mechanism are good, I just need to figure out why the other two are not responding.  No changes to the system other than the upgrade to OPNsense.
Minisforum UN100D, N100, 8GB, 256GB nVME w/ZFS

One of the three reverse proxies stopped working yesterday, so I need to look into what is going on with those, I thought I had it fixed permanently.

Any suggestions on where to look or troubleshooting tips to try when Caddy stops responding?
Minisforum UN100D, N100, 8GB, 256GB nVME w/ZFS

If caddy stops responding look into

/var/log/caddy/caddy.log

See if there is a panic crash (this will not show in the logs you see in the GUI).
Hardware:
DEC740

Awesome, thank you so much!  I'll look into that and report back.
Minisforum UN100D, N100, 8GB, 256GB nVME w/ZFS

No panics in the log.

Older entries contained a typical complaint about the inability to increase the buffer size, but lately there are only info messages about GOMAXPROCS and GOMEMLIMIT, and warn messages about "No files matching import glob pattern".
Minisforum UN100D, N100, 8GB, 256GB nVME w/ZFS

I would try to get help in the caddy community with your Caddyfile and Debug logs.

502 sounds like it happens on the HTTP layer so might be an issue with your particular infrastructure.

The caddy version changed in that upgrade so maybe theres an issue there.

https://caddy.community
Hardware:
DEC740

Good advice.  Thank you for the link.
Minisforum UN100D, N100, 8GB, 256GB nVME w/ZFS