Timeout issue on renewal

Help
1

Coming back to an old server - over 6 months since last login but it was set to auto-renew (and failed to do so)

  • I am connecting to this server fine without timeouts via terminal, browser, Filezilla, etc

  • I have confirmed DNS A record points to correct ip address

  • I have confirmed port 80 is open

  • I am using ufw with Apache Full ALLOW Anywhere (and v6)

  • I did have ssl redirect enforced (which could(?) result in fail because of out-of-date cert) but I have already retried with redirect removed, same problem

  • have reviewed other answers on similar issues, none have provided anything I can use to progress further

  • short of full LAMP re-install ... ??

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. crt.sh | 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: airinteract.net

I ran this command: certbot --apache -v

It produced this output:
Certificate is due for renewal, auto-renewing...
Renewing an existing certificate for airinteract.net and www.airinteract.net
Performing the following challenges:
http-01 challenge for airinteract.net
http-01 challenge for www.airinteract.net
Waiting for verification...
Challenge failed for domain airinteract.net
Challenge failed for domain www.airinteract.net
http-01 challenge for airinteract.net
http-01 challenge for www.airinteract.net

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: airinteract.net
Type: connection
Detail: 52.91.193.209: Fetching http://airinteract.net/.well-known/acme-challenge/dPuyyNRtpXPFi7ksNGWeCUcC-iU9_H-2s0VuJfg6gJ0: Timeout during connect (likely firewall problem)

Domain: www.airinteract.net
Type: connection
Detail: 52.91.193.209: Fetching http://www.airinteract.net/.well-known/acme-challenge/wtHEcucCoTEW3LSjLwg9XtaTpWT7XABzKl1aSqISLsU: Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

Cleaning up challenges
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version):
Apache/2.4.52

The operating system my web server runs on is (include version):
Ubuntu 22.04.4 LTS

My hosting provider, if applicable, is:
AWS

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):
certbot 1.21.0

2

@NickNalder , welcome to the community!

The connection to the host airinteract.net is timing out:

tumbleweed:~ # curl -s -v 'http://airinteract.net/' > /dev/null
* Host airinteract.net:80 was resolved.
* IPv6: (none)
* IPv4: 52.91.193.209
*   Trying 52.91.193.209:80...
* connect to 52.91.193.209 port 80 from 192.168.1.2 port 56416 failed: Connection timed out
* Failed to connect to airinteract.net port 80 after 132896 ms: Couldn't connect to server
* Closing connection
tumbleweed:~ #

There may be still firewall issue, or the IP address is incorrect.
What does the command curl -s -4 ifconfig.co gives as output?

5 Likes
3

Hi @bruncsak

I did get a response from ifconfig but was in the process of trying to install a web browser into my ubuntu server terminal environment to read the response when I realised that the problem is likely my AWS security settings (so yes - a firewall, but not one I was thinking about in terms of my on-server setup).

I can access fine from any of my devices, but they are all coming in from my ISP which is probably whitelisted (this was a dev-only site, so I did not want it open to the web as a whole)

I will fix that and am then pretty certain that will resolve the problem
May thanks, will let you know if not!

3 Likes