Some ISP’s prevent or block Inbound port 80 for some security reasons, mainly, related to the client’s router’s web based configurations, TEData in Egypt is an example. Your verification process is carried out through port 80, to finally, allow https through port 443. The question here: Why only t…

Hi, I believe that topic was being discussed before… (I’ll find the topic & replace this line) The ports are only limited to port 80 because that’s the standard port… However users could make a redirect from 80 to other ports… (It’s a myth that let doesn’t allow port 8080…) Ports other than 80,8…

As I regarded my ISP block port 80 Inbound traffic at all, so LE will not able to access the server. I have freemyip.com dynamic dns and there is no way to use DNS validation for it.

It should be possible to use port 443 for authentication again since 8 days ago, when the tls-alpn-01 challenge was enabled in production . This new challenge should also be supported in certbot version 0.25.0 , but has partially been removed in version 0.25.1 .

[image] Osiris: This new challenge should also be supported in certbot version 0.25.0 , but has partially been removed in version 0.26.0 . I think this support is limited to the acme module & allowing the challenge type to be parsed. I don't believe there is a Certbot version available that can…

[image] stevenzhu: I believe that topic was being discussed before… Again, and again, and again... [image] Why does HTTP validation have to be done on port 80? Help I… [image] HTTP validation failed when only port 443 is open Server I……

[image] saidbakr: I have freemyip.com dynamic dns and there is no way to use DNS validation for it. If you have the ability to set up a CNAME record with them, then you can use DNS challenges by pointing that record to either your own server and run acme-dns, or to a free DNS provider that h…

You can either use a DDNS that supports DNS validation, like Dynu, or somehow find a way to unblock port 80 or 443. Otherwise, Let’s Encrypt cannot support your use case and you need to look elsewhere.

Verification on non standard port 80

Feature Requests

danb35 July 20, 2018, 9:14pm 7

Again, and again, and again...

...and no doubt others as well.

Topic		Replies	Views
ISP blocks port 80 Help	7	5103	April 4, 2019
Support for ports other than 80 and 443, v3 Feature Requests	10	32564	June 6, 2018
Tls alpn challenge on non-standard https port (8080) Help	4	2768	March 12, 2019
Domain validation on 80 and 443 but no override? Server	13	5063	October 25, 2016
Get Let's Encrypt Certificates With Blocked Ports by ISP Help	4	4563	September 4, 2017

Verification on non standard port 80

Related topics