Certbot-auto renew error network is unreacheable

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: vqure

I ran this command: /usr/local/bin/certbot-auto --nginx -d vqure.com -d www.vqure.com certonly

It produced this output: Your system is not supported by certbot-auto anymore.
certbot-auto and its Certbot installation will no longer receive updates.
You will not receive any bug fixes including those fixing server compatibility
or security problems.
Please visit https://certbot.eff.org/ to check for other alternatives.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
An unexpected error occurred:
ValueError: Requesting acme-v02.api.letsencrypt.org/directory: Network is unreachable
Please see the logfiles in /var/log/letsencrypt for more details.

My web server is (include version): nginx

The operating system my web server runs on is (include version): ami linux 1

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.10.1

Your server needs outbound network access to talk to the Let's Encrypt servers to request a certificate.

1 Like

thanks for reply peter already we allowed all outbound traffic on server.

1 Like

Well, that's just what "network is unreachable" is saying. It's not able to reach the network where Let's Encrypt's servers are. You may want to try accessing it through other commands (curl https://acme-v02.api.letsencrypt.org/directory or the like) or seeing what other outbound sites you can access to help narrow down what's going on.

1 Like

Hi @ajayjha welcome to the LE community forum :slight_smile:

certbot-auto is deprecated and you should remove it and then install a newer version of certbot.

Then show us the new error message from certbot.
OR as @petercooperjr suggested:

if you see for this site it is showing network unreachable.

output of curl command:-
curl https://acme-v02.api.letsencrypt.org/directory -v

  • Trying 172.65.32.248...
  • TCP_NODELAY set
  • Trying 2606:4700:60:0:f53d:5624:85c7:3a2c...
  • TCP_NODELAY set
  • Immediate connect fail for 2606:4700:60:0:f53d:5624:85c7:3a2c: Network is unreachable
  • Trying 2606:4700:60:0:f53d:5624:85c7:3a2c...
  • TCP_NODELAY set
  • Immediate connect fail for 2606:4700:60:0:f53d:5624:85c7:3a2c: Network is unreachable
  • Trying 2606:4700:60:0:f53d:5624:85c7:3a2c...
  • TCP_NODELAY set
  • Immediate connect fail for 2606:4700:60:0:f53d:5624:85c7:3a2c: Network is unreachable
  • Trying 2606:4700:60:0:f53d:5624:85c7:3a2c...
  • TCP_NODELAY set
  • Immediate connect fail for 2606:4700:60:0:f53d:5624:85c7:3a2c: Network is unreachable
  • Trying 2606:4700:60:0:f53d:5624:85c7:3a2c...
  • TCP_NODELAY set
  • Immediate connect fail for 2606:4700:60:0:f53d:5624:85c7:3a2c: Network is unreachable
  • Trying 2606:4700:60:0:f53d:5624:85c7:3a2c...
  • TCP_NODELAY set

Try:
curl -Iv4 https://acme-v02.api.letsencrypt.org/directory
curl -Iv4 https://google.com
curl -Iv6 https://google.com

And show the output of:
curl -4 ifconfig.co
curl -6 ifconfig.co

curl -4 ifconfig.io ---> not any response

curl -6 ifconfig.io
output:-
curl -6 ifconfig.co
curl: (7) Couldn't connect to server

And the other commands suggested by Rudy?

In any case I think this is more generic networking issue than something specifically related to Let's Encrypt..

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.