Hi Guys,
I wonder if I might ask for some help?
I run a mail server behind a Caddy reverse proxy which is hosted on a DEC850 device running opnsense 26.1.8_5. Today, I upgraded firmware to opnsense 26.7, and the experience was great, and everything appeared to be working, except the 3rd party plugin for Caddy.
The Outbound NAT configuration carried over perfectly from the upgrade, and from what I could see, so did all of the firewall rules. I've attached the Caddy file for inspection (although it does appear that I'm bullying Caddy, it's the proxying of HTTP and HTTPS ports that stopped working, so my suspicions are aroused. I've watched Poirot, so I've some idea how to pursue a thread, but not the slightest idea how to fix it).
Is there anything easy that you think I might be missing? If so, though lacking professional expertise, I have the vigor of an enthusiast, so I'm ready to try anything I can understand or research.
(I've temporarily rolled back for now, but I'm learning about a work-around whereby I might proxy the HTTPS port via Caddy hosted on Kubernetes on the email server host).
Again, very pleased with the upgrade, but I've just this one sticking point where I think I may have tied myself in knots. Any help appreciated. I'll supply any relevant info. Not to worry if it's too much a pain, since I can always run with my Plan B and upgrade to the latest opnsense anyway.
Thanks again for your time, and great work on the firmware.
Try disabling KTLS:
sysctl kern.ipc.tls.enable=0
I had issues with NGINX reverse proxying (HAProxy was also having problems) after the update, this resolved the issue. You can re-enable it with a =1, or just reboot, as this command will not survive a reboot.
Many thanks! Will try it!
Found my issue, and my configuration of Caddy is absolved of guilt in the end. A Destination NAT rule was set to "Manual", instead of "Register Rule." Once that was fixed, everything with 26.7 worked for me :o)
Many thanks for your help!