Failed to connect to acme-v02.api.letsencrypt.org port 443 after 130393 ms: Connection timed out

Help
1

I'm trying to get a cerificate for the domain delirium.freemyip.com
The VPS I'm using, times out when connecting to https://acme-v02.api.letsencrypt.org/directory

Command certbot certonly --standalone --preferred-challenges http -d delirium.freemyip.com returns error:
An unexpected error occurred:
ValueError: Requesting acme-v02.api.letsencrypt.org/directory: Network is unreachable
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 domain is: delirium.freemyip.com

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

It produced this output: Failed to connect to acme-v02.api.letsencrypt.org port 443 after 130393 ms: Connection timed out

My web server is (include version): 3x-ui

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

My hosting provider, if applicable, is: Not applicable (VPS)

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

1 Like
2

Welcome to the Let's Encrypt Community! :slightly_smiling_face:

Do you have outbound access enabled for port 443?

3 Likes
3

Hi! Yes, I have. Due to some problems I did it for several domens yesterday and it worked fine. I suspect that my ip might have been blocked because of this
ps sorry, forgot to mention it in topic

2 Likes
4

I could be wrong, but I don't think "network is unreachable" is the error you receive if your IP address has been blocked.

4 Likes
5

Maybe. That was my guess

1 Like
6

A similar situation:

2 Likes
7

There was firewall problem. I tried to shutdown it and it didn't help

1 Like
8

The problem was in my local dns cache. After cleaning i was able to get the certificate

3 Likes