Just tried this and ran into an issue.
Before I spun up an instance of geldim/https-redirect:latest outside of my load balancer and told it to run on every host. This worked, though it was a bit hacky and opens 80 unnecessarily in some places.
Today I tried adding it into a load balancer with both 80 and 443 open (443 was only open previously.) I have a rule with no hostname set, port 80 open, redirecting to geldim/https-redirect:latest port 80. Every other rule has a hostname and port 443 set as the source.
If I hit, say, http://ci.thewordnerd.info, sometimes it shows the HTTP redirect, sometimes I get a 503. They’re hosted behind Cloudflare but I see this even when hitting the VM directly and setting the Host: header manually. All hosts seem to work if I hit them via https.
How can I provide additional information to help resolve this? Would you like my rancher-compose definition just as a reference, even though compose can’t spin up load balancers yet? Or should I get the haproxy.cfg from the balancer instance? Let me know.