requests.exceptions.ConnectionError: HTTPSConnectionPool

Hmmm, is my IP & blocked?

requests.exceptions.ConnectionError: HTTPSConnectionPool(host='', port=443): Max retries exceeded with url: /directory (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0xffffb13004e0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
Ask for help or search for solutions at See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

letsencrypt.log: debian Pastezone

i hope somone can help me.

Please fix the DNS resolving capabilities of the host running Certbot. The error points to a DNS resolving problem.

Also, perhaps it's a good idea to edit the title of your thread to something better suited: the URI of an unrelated issue is probably not the best one.


Thanks for your reply. The Host ist running under debian vm -> docker -> nginx proxy manager.
container network: bridge

i have forwarded the port 80&443 to my debian vm. The Domain was added under pi-hole DNS and Cloudflare. I have no clue why i get an dns problem :frowning:

1 Like

It's a generic DNS problem: your container running Certbot probably can't resolve any host. (E.g., the command ping would probably fail too..) Please search for Docker and DNS issues on the internet (I'm not familiair with the workings of Docker myself). Or just search for the error "Temporary failure in name resolution" on this Community.


Ping is working! Now i get this msg :frowning:

[10/21/2022] [6:23:26 PM] [Express ] › :warning: warning Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-12" --agree-tos --authenticator webroot --email "" --preferred-challenges "dns,http" --domains ""
Saving debug log to /var/log/letsencrypt/letsencrypt.log
An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see Failed Validation Limit - Let's Encrypt
Ask for help or search for solutions at See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

That means you've tried too many times and failed. See the linked rate limit page for how long you're limited.

Unfortunately, this error also obfuscates the actual error what's causing the validation to fail to begin with.

You should switch to the staging environment and debug why the challenge is failing. Only when the challenge is succeeding, you should change back to the production environment to get your cert.


I see:

But no specific web root path is being provided.


i use Nginx Proxy Manager:

There lies part of the problem:
NPM is difficult to troubleshoot.


npm is just terrible.


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