OPNsense Forum

English Forums => General Discussion => Topic started by: collinsit on March 05, 2026, 05:05:59 PM

Title: Some Caddy sites not working after update
Post by: collinsit on March 05, 2026, 05:05:59 PM
Good morning, I just did an update to my Opnsense firewall. Everything seems ok but I have one site that redirects through the Caddy plugin that is now failing. It was working previously and just stopped after the update. I looked at the updates that were done and it looks like Caddy updated to 2.1.0 as part of the update. From what I can tell, all the other sites are working fine, it is just this one which is a pretty standard HTTPS site so I am not sure why it has stopped.

I changed the DNS records so the connection points directly to the server, not going through Caddy and it works fine that way but as soon as I point it to Caddy again, it stops. I have looked at the logs on the firewall and am not seeing any real errors related to this either.

The error I am seeing in the web browser is.

Not Found
HTTP Error 404. The requested resource is not found.

Any suggestions?

Thanks

Neal
Title: Re: Some Caddy sites not working after update
Post by: Monviech (Cedrik) on March 05, 2026, 05:08:00 PM
https://forum.opnsense.org/index.php?topic=51162.0

Title: Re: Some Caddy sites not working after update
Post by: collinsit on March 05, 2026, 05:21:50 PM
You are a rockstar, that worked great. Not sure why it only affected one of the sites I have hosted though.

Should I change that on all the handlers or is it one of those things that if it is working, don't bother messing with it?
Title: Re: Some Caddy sites not working after update
Post by: Monviech (Cedrik) on March 05, 2026, 05:27:22 PM
Most likely affects only tls insecure skip verify upstreams.

Not broadly applicable to all of them, HTTP only or "real" TLS with server name shouldnt be affected.
Title: Re: Some Caddy sites not working after update
Post by: collinsit on March 05, 2026, 05:33:07 PM
Fair enough, i'll leave them unless they are broken. My headers all connect to the upstream servers by IP though as I didn't want to deal with DNS issues or certificate issues on the upstreams so all sites are using the skip tls insecure but this is the only one that seemed to break.

Thanks again for the quick help.