Website on custom port

[andreas.hoffmann]

I am trying to find out, if I can use let’s encrypt in my setup:

We are running a production-server and several test-servers behind a single IP.
For this, port 80 is routed to a webserver that responds with the appropriate redirect:
For production: https://application.mydomain.com
For testing: https://applicationtest_x.mydomain.com:2044x

We then use the port to route the request to the appropriate webserver.

Since I thought that the CA follows redirects, I expected it to work. But during authorization, certification for the custom ports is rejected.

Is this an error on my side or is this the expected result for this case?

[danb35]

@andreas.hoffmann

Is this an error on my side or is this the expected result for this case?

This is the expected result. LE will follow redirects, but only to (1) a different host, or (2) HTTPS. They won't follow redirects to other random ports.

[Osiris]

And, for as far as I know, (3) different paths (i.e., from /.well-known/acme-challenge/ to /foo/bar/). Not sure about the filename though.

The answer might even be “everything but the port”

[_az]

Everything but the port and also (4) not raw IP addresses.