1. The problem I’m having: I cannot set new bindings in the “listen”-section of a server if both of these conditions occur: the server is configured to disable automatic HTTPS redirects the new address is part of the old one (0.0.0.0:443 → 172.17.0.1:443) Is this behavior intended? 2. Error mess…

A workaround I figured out was to first delete the :443 address in the “listen” section and then set the new address.

I don’t think it’s intentional. @Mohammed90 what do you think? I probably need to adjust the listener usagepool to account for catch-all addresses or something?

I don’t see how this could work. Caddy is designed to do graceful reloads by keeping the first config running until the second one is ready to go. Caddy hands off the listeners from the previous to the next config if they’re the same, but if they differ then that handoff is not possible and the new …

That is true… I think there might be a socket option at least on Linux we can set to enable this behavior. Not sure how to do it for Windows/Mac.

I agree with @francislavoie in his reasoning that the issue is overlapping listener addresses. There’s the SO_REUSEADDR option which could resolve the issue: The SO_REUSEPORT socket option [LWN.net] One of the features merged in the 3.9 development cycle was TCP and UDP support for th…

Caddy Community

Release old bindings when HTTPS redirects are disabled

Help

show post in topic

Home
Categories
Guidelines
Terms of Service

Powered by Discourse, best viewed with JavaScript enabled