# My IP is blocked

**URL:** <https://community.letsencrypt.org/t/my-ip-is-blocked/182344>\
**Category:** Help\
**Created:** [August 4, 2022, 5:24pm UTC](https://community.letsencrypt.org/t/my-ip-is-blocked/182344 "2022-08-04T17:24:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![joneiseman](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@joneiseman](https://community.letsencrypt.org/u/joneiseman)\
**Post date:** [August 4, 2022, 5:24pm UTC](https://community.letsencrypt.org/t/my-ip-is-blocked/182344/1 "2022-08-04T17:24:24Z")

</div>

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. [https://crt.sh/?q=example.com](https://crt.sh/?q=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:ourfamilybios.com

I ran this command:  
certbot --apache -d [ourfamilybios.com](http://ourfamilybios.com) -d [www.ourfamilybios.com](http://www.ourfamilybios.com)  
It produced this output:  
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='[acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)', port=443): Max retries exceeded with url: /directory (Caused by NewConnectionError('\<urllib3.connection.VerifiedHTTPSConnection object at 0x7ff649b3bc50\>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))

I ran this command: ping [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)  
It produced this output:  
ping: [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org): Temporary failure in name resolution

My web server is (include version):

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

My hosting provider, if applicable, is: hostinger (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): 0.27.0 (I can't update the Certbot version because I can't install snap)

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [August 4, 2022, 5:26pm UTC](https://community.letsencrypt.org/t/my-ip-is-blocked/182344/2 "2022-08-04T17:26:26Z")

</div>

No, your IP is **NOT** blocked (at least not that we can tell from this information), your DNS is failing as the error message clearly states. Please fix your DNS and try again.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [August 4, 2022, 5:34pm UTC](https://community.letsencrypt.org/t/my-ip-is-blocked/182344/3 "2022-08-04T17:34:44Z")

</div>

> [@joneiseman](#):
>
> Temporary failure in name resolution

I agree.  
That's a DNS problem.

---

<div class="post-metadata">

**Author:** ![joneiseman](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@joneiseman](https://community.letsencrypt.org/u/joneiseman)\
**Post date:** [August 4, 2022, 6:14pm UTC](https://community.letsencrypt.org/t/my-ip-is-blocked/182344/4 "2022-08-04T18:14:53Z")

</div>

Thanks for the clue. I was able to fix the DNS problem.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [September 3, 2022, 6:15pm UTC](https://community.letsencrypt.org/t/my-ip-is-blocked/182344/5 "2022-09-03T18:15:49Z")

</div>

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