Hello I got http://my.domain.com and https://my.domain.com pointing to a dummy index.html. Which is accessible via the internets. So both port 80/443 should be properly forwarded. Trying to run: sudo certbot certonly -w /var/www/html -d my.domain.com And then I select 2: Place files in webroot …

It would be easier to help if you provided your domain name. If you really don't want to do that, maybe try checking it yourself with https://letsdebug.net/ and see if that comes up with anything useful. [image] hazyred: (unrelated, how do I get this prompt to go away and automatically default …

[image] hazyred: Any suggestions on what I can try to see what’s not working well? You could also try from a system outside your "same network".

It seems the simplest answer is the correct one in this case. Port 80 is blocked by the ISP :frowning:. So I guess that means http-01 is out of the question. I probably should of tried this simple test first before asking… I can’t add a txt record, so there goes dns-01. And if I understood correct…

[image] hazyred: Port 80 is blocked by the ISP The ISP blocks port 80 and allow 443? Well that's a first! An ISP that forces HTTPS... While (for security reasons) this CA is now forced to only issue certs via port 80 (not 443). Catch 22 at it's finest.

[image] hazyred: I can’t add a txt record, so there goes dns-01. Are you using dynamic DNS? If so would you be willing to switch to a different dynamic DNS service? (Of course that would mean using a different domain name). There are a few such as dynu and duckdns that are supported by acme.s…

Btw, this is for a server that I have at home and I wanted to switch the self signed cert to a real one. @rg305 It’s a residential service, they explicitly and historically block port 80 to not allow people hosting their own stuff. @jmorahan I was using *.mynetgear.com since it was configurable …

[image] rg305: Well that’s a first! An ISP that forces HTTPS… I think we've seen quite a few people with this problem here (they generally then had to switch to DNS-01 validation). I'm not sure if anyone's drawn up a list of affected ISPs.

[image] hazyred: I will try dynu with their little client on the server and see how it goes. I’m not attached to the domain name, so no loss there In that case this recent tutorial may also help.

Thanks for the help and suggestions, finally I got things working with dns-01.

Timeout during connect

Help

jmorahan May 7, 2018, 9:39pm 9

In that case this recent tutorial may also help.

Topic		Replies	Views
Certbot times out Help	9	1903	April 16, 2019
Timeout during connect Help	16	1875	July 5, 2021
Timeout during connect (likely firewall problem) Help	18	2784	August 31, 2022
Timeout during connect (likely firewall problem) Help	5	5787	August 4, 2020
Timeout during connect Help	5	741	September 10, 2018

Timeout during connect

Related topics