Unable to obtain auto TLS on custom HTTPS port

[AxelTheGerman]

This is similar to #26 but I'm running the proxy on a custom HTTPS port - as I have another service running on 443.

I read that

the docs mention you only need 443 port open to set up SSL

but I can't find this anywhere.

Does that mean --https-port breaks auto TLS? Or is there a way this can still work.

[kevinmcconnell]

We support the HTTP-01 challenge type now. So the auto TLS will work if you have HTTP listening on port 80, and/or HTTPS listening on 443. As long as one of those ports is available, you should be free to change the other port to whatever you want.

(I've just sanity-checked this by running the proxy with --https-port=4433 and successfully establishing TLS on that port.)

It's not possible to actually do the ACME challenge on a non-standard port, but since we support both HTTP-01 and TLS-ALPN-01 that means that having either of the standard ports available is enough.