Lets Encrypt blocked on 2 IP's I'm using

It seems Letsencrypt.org is blocked on 2 IP's I am trying to set up.

My domain is:
164.67.xxx.xxx
164.67.xxx.xxx

I ran this command: curl -I https://acme-v02.api.letsencrypt.org/

It produced this output: Failed to connect to acme-v02.api.letsencrypt.org port 443: No route to host

My web server is (include version): PHP 8.3.3

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

My hosting provider, if applicable, is: University

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): Nextcloud, Nginx Proxy Manager

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

Hello @dukeside, welcome to the Let's Encrypt community. :slightly_smiling_face:

Let’s Encrypt offers Domain Validation (DV) certificates and not certificates for IP Addresses.

Those are IP Addresses and not Domain Names.

Thus you need to own and have control over the Domain Name (or have a subdomain under an existing domain name, for example pointed to your server by your employer or school) you wish to obtain a certificate for, from an ICANN Accredited Registrar.

Please update your Certbot current release is Certbot 2.9.0 Release
See Certbot Instructions | Certbot

Also please see Certificates for localhost - Let's Encrypt

1 Like

Most likely you're routing the route to 172.64.0.0/13 incorrectly. This is often caused by network admins incorrectly routing the private route 172.16.0.0/12 by using an incorrect network mask.

It's almost certainly not due to Let's Encrypt blocking your IP address (why does everybody always jump to that conclusion?)

6 Likes

Probably because human nature seems to be blame the environment outside of their control first. :frowning:

2 Likes

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