letsencrypt integration does not use configured internal server port

[illuminatedg]

I just tried configuring letsencrypt integration and generating a cert but the request is being made without the port I configured in the Let's Encrypt page:

filezilla-letsencrypt.png (13.76 KiB) Viewed 649 times

Has anyone else tried generation with any port besides 80? The docs state that other ports should work but the two pages don't seem to be linked up properly https://filezillapro.com/docs/server/ad ... web-server

[oibaf]

Let's Encrypt® itself will only contact the host on port 80, that will not change.

However, on your end you might have set up port forwarding to any other internal address and port, hence why FileZilla Server gives you the flexibility to set up different listeners.

[botg]

ACME services always use port 80 to access the hostnames specified in the certificate request during the validation process, they cannot use other ports.

FileZilla Server let's you listen on arbitrary ports, for example to handle situations in which port 80 is already in use on the local machine. Regardless which port you configure, you need to make sure to route the traffic, or the HTTP requests, so that requests to .well-known/acme/challenge on port 80 of the entered hostnames are being delivered to FileZilla Server on the configured port.

[illuminatedg]

I was starting to figure that might be the case. With ACME only working on 80 I'll look into adding proxying to my webserver ( probably best not to ask ) to get requests on that subdomain over to filezilla server.

Thanks for the responses!