Timeout During Connect

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: naspibagel.page

I ran this command: sudo certbot --apache
Then of course I chose my domain

It produced this output:
Domain: naspibagel.page
Type: connection
Detail: Fetching
http://naspibagel.page/.well-known/acme-challenge/6fUwpMM9Wsi8MWGCQZVokdDj088GiMDm_NmZ_WKXZO0:
Timeout during connect (likely firewall problem)

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

My web server is (include version): Apache2.4.38

The operating system my web server runs on is (include version): Raspbian

My hosting provider, if applicable, is: Google Domains

I can login to a root shell on my machine (yes or no, or I don't know): Yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): No

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 0.31.0

I think I'm getting a timeout error because of port 80. I can't seem to get it to forward correctly. I have verified with my ISP and my router manufacturer that they are not blocking port 80. I have configured port forwarding on 80 through my router as they suggested. I am having no problems forwarding port 443 and it is configured the same way 80 is. I've also allowed 80 and 443 on ufw and have a static ip.

sudo ufw status
Status: active

To Action From


22 ALLOW 192.168.0.28
80 ALLOW Anywhere
443 ALLOW Anywhere
80 (v6) ALLOW Anywhere (v6)
443 (v6) ALLOW Anywhere (v6)

Nonetheless, there are multiple confirmations from different sources that Suddenlink does block port 80 on residential connections: https://duckduckgo.com/?q="suddenlink"+"port+80".

It does seem like the most likely cause.

1 Like

Well it seems as though I can't get an open port 80 without giving Suddenlink money so it must be bypassed.

I've decided to try a DNS-01 challenge but even attempting that gives me errors saying I need to check that a DNS record exists for my domain. I have an A record so I'm not sure what the issue is.

I issue this command,

sudo certbot certonly --manual --manual-auth-hook /etc/letsencrypt/acme-dns-auth.py --preferred-challenges dns --debug-challenges -d *.naspibagel.page -d naspibagel.page

and get this response

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Obtaining a new certificate
Performing the following challenges:
dns-01 challenge for naspibagel.page
dns-01 challenge for naspibagel.page


NOTE: The IP of this machine will be publicly logged as having requested this
certificate. If you're running certbot in manual mode on a machine that is not
your server, please ensure you're okay with that.

Are you OK with your IP being logged?


(Y)es/(N)o: y
Output from acme-dns-auth.py:
Please add the following CNAME record to your main DNS zone:
_acme-challenge.naspibagel.page CNAME 9164f06f-48f3-4c51-98eb-156484df9bd1.auth.acme-dns.io.

Waiting for verification...


Challenges loaded. Press continue to submit to CA. Pass "-v" for more info about
challenges.


Press Enter to Continue
Cleaning up challenges
Failed authorization procedure. naspibagel.page (dns-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.naspibagel.page - check that a DNS record exists for this domain, naspibagel.page (dns-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.naspibagel.page - check that a DNS record exists for this domain

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: naspibagel.page
    Type: None
    Detail: DNS problem: NXDOMAIN looking up TXT for
    _acme-challenge.naspibagel.page - check that a DNS record exists
    for this domain

    Domain: naspibagel.page
    Type: None
    Detail: DNS problem: NXDOMAIN looking up TXT for
    _acme-challenge.naspibagel.page - check that a DNS record exists
    for this domain

Did you create this CNAME record in your Google DNS interface?

Try the process again, and create the record that is shown, before continuing further.