Much appreciated stranger. Hopefully now I can stop exposing the two most attacked ports in existence from my LAN XD.

Boo, no idea why acme forces these specific ports. Swapping them seems like a pretty basic obfuscation technique that could help a lot to secure any services.

Edit: actually seems like this might be possible with the dns challenge type. I’m gonna test this out later https://github.com/caddy-dns/porkbun

How do u use a port other than 443 for https. AFAICT all web browsers are pinned to it (for ssl checks I think) and I could never get an actual https connection through an alt port. Maybe I didn’t understand it properly.

Edit: I think actually it’s the auto cert provisioning workflow. The CA I’m signing against hardcodes port 443 :/

Edit, edit: this was the issue https://caddy.community/t/non-standard-ports-for-https/6916/4