I have tried to renew my certificate, the way I have done it many times every three months, using [certbot --force-renewal] (if there is a better way, pls let me know). This time, for the first time, I got the [Challenge failed for domain] error message and I have no idea why and what to do. The server is remote and the people there are not able to help, so far. Can someone offer me some advice and point me in the right direction? Any help is much appreciated! Thanks!
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Which names would you like to activate HTTPS for?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: travelintaiwan.net
2: www.travelintaiwan.net
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel):
Renewing an existing certificate for travelintaiwan.net and www.travelintaiwan.net
Performing the following challenges:
http-01 challenge for travelintaiwan.net
http-01 challenge for www.travelintaiwan.net
Waiting for verification...
Challenge failed for domain travelintaiwan.net
Challenge failed for domain www.travelintaiwan.net
http-01 challenge for travelintaiwan.net
http-01 challenge for www.travelintaiwan.net
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: travelintaiwan.net
Type: connection
Detail: 211.79.207.183: Fetching
http://travelintaiwan.net/.well-known/acme-challenge/htFaZNpQmU6fHjWYZ_eVa0rkTJCRV7HztnazAT1O_q4:
Connection refused
Domain: www.travelintaiwan.net
Type: connection
Detail: 211.79.207.183: Fetching
http://www.travelintaiwan.net/.well-known/acme-challenge/6tLOkY9bRjaT_bp_V1cYO_WjllUDpI_VclCi6gqQmuU:
Connection refused
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):
The operating system my web server runs on is (include version): Centos 7
My hosting provider, if applicable, is:
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.11.0
I can also reach your domain and even tested from several locations around the world and they all worked. I also tried with the same "user-agent" string as Let's Encrypt as the Palo Alto brand of firewall might block those requests. But, those tests also worked so it is not that.
It looks more like an IP based firewall blocking Let's Encrypt and the Let's Debug IP addresses.
Can you check logs for right around the time of a test using Let's Debug? See if your server can see the connection being refused somehow?
(I'm not sure what logs to suggest looking at, since "connection refused" is more often OS-level rather than application-level... you might need to run something like tcpdump on the server!)
www.travelintaiwan.net has an A (IPv4) record (211.79.207.183) but a request to this address over port 80 did not succeed. Your web server must have at least one working IPv4 or IPv6 address.
What could be the reason why the request did not succeed, if it's not an IP based firewall blocking LE?
Successfully received certificate.
Certificate is saved at: /etc/ssl-com/live/travelintaiwan.net/fullchain.pem
Key is saved at: /etc/ssl-com/live/travelintaiwan.net/privkey.pem
This certificate expires on 2023-12-20.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.
Deploying certificate
Successfully deployed certificate for travelintaiwan.net to /etc/httpd/conf.d/travelintaiwan-le-ssl.conf
Congratulations! You have successfully enabled HTTPS on https://travelintaiwan.net
But in the browsers it's not accepted it seems. Is there a waiting period?
As you can see, I used ssl.com (SSL Dragon), not sure if that is a competitor to Let's Encrypt? I hope this has not disqualified me from asking questions here. I just want to get this to work. Will be happy to use whatever provider. Tks, guys!
It's not IN your HTTP configuration. Certificate chains are specified at the server. It's not that the browser is not "accepting" the new, it's just that you haven't restarted your HTTP server, so the new certs aren't being sent. In my experience, on self-hosted systems, certbot does that, but perhaps it can't in your configuration.