Check if IP is blocked (129.213.132.1)

Urgent

my IP 129.213.132.1

@Meriem-BM My best guess is that Let's Encrypt servers are not blocking requests from your IP.

I say this because I cannot contact that IP from my own test server. So, it is not receiving inbound requests. That looks like a general comms problem from your system and not unique to specific blocks. I only see port 22 open to that IP

nmap 129.213.132.1 -Pn
PORT   STATE SERVICE
22/tcp open  ssh

Can you explain why you think your IP is blocked? What exactly is the error message? Blocks are rare. Comms config problems are far more likely.

If you want help we will need more info. Please fill out the form you were shown as best you can

===========================

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:

I ran this command:

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:

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

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

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

4 Likes

Using https://check-host.net/
Permanent link to this check report

1 Like

From location 1

1>nmap -Pn 129.213.132.1
Starting Nmap 7.93 ( https://nmap.org ) at 2022-11-19 17:27 UTC
Nmap scan report for 129.213.132.1
Host is up.
All 1000 scanned ports on 129.213.132.1 are in ignored states.
Not shown: 1000 filtered tcp ports (no-response)

Nmap done: 1 IP address (1 host up) scanned in 413.49 seconds

From location 2

$ nmap -Pn 129.213.132.1
Starting Nmap 7.80 ( https://nmap.org ) at 2022-11-19 17:25 UTC
Nmap scan report for 129.213.132.1
Host is up.
All 1000 scanned ports on 129.213.132.1 are filtered

Nmap done: 1 IP address (1 host up) scanned in 201.54 seconds
1 Like

Also I find no Domain Name that maps to 129.213.132.1
Let’s Encrypt offers Domain Validation (DV) certificates which implies a Domain Name.

1 Like

This really is the question. @Meriem-BM, it's exceedingly rare for Let's Encrypt to block an IP address or block, so it's therefore highly unlikely that's the cause of whatever problem you're experiencing. But if you'll let us know, in detail, just what problem you are experiencing, we can likely help you.

5 Likes

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