Max retries exceeded with url: /directory (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f946c61c9a0>: Failed to establish a new connection: [Errno -3] Try again'))

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. |, 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: I setup linuxserver/SWAG Docker

It produced this output: Everything runs fine but i get this error "

An unexpected error occurred:
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='', port=443): Max retries exceeded with url: /directory (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f946c61c9a0>: Failed to establish a new connection: [Errno -3] Try again'))
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.
ERROR: Cert does not exist! Please see the validation error above. Make sure you entered correct credentials into the /config/dns-conf/duckdns.ini file.

" The Linuxserver team said i shoudl ask LetsEncrypt they have no idea.

The operating system my web server runs on is (include version):
Debian GNU/Linux 11 (bullseye)

My hosting provider, if applicable, is: Selfhosting , its running in my docker network i also use Adguard as my DNS , i setup the Adguard dns in the docker-compose and also the as a backup.
Port 443 and Port 80 are also opened on my Fritzbox. (The Docker is running on Port 85 : 445)

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

curling the site works just fine

root@docker:~# curl -v
*   Trying 2606:4700:60:0:f53d:5624:85c7:3a2c:443...
* Connected to (2606:4700:60:0:f53d:5624:85c7:3a2c) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject:
*  start date: Mar  1 18:47:14 2023 GMT
*  expire date: May 30 18:47:13 2023 GMT
*  subjectAltName: host "" matched cert's ""
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x557eef35e2e0)
> GET /directory HTTP/2
> Host:
> user-agent: curl/7.74.0
> accept: */*
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
< HTTP/2 200 
< server: nginx
< date: Fri, 28 Apr 2023 07:23:39 GMT
< content-type: application/json
< content-length: 756
< cache-control: public, max-age=0, no-cache
< x-frame-options: DENY
< strict-transport-security: max-age=604800
  "HuxON2xe8fA": "",
  "keyChange": "",
  "meta": {
    "caaIdentities": [
    "termsOfService": "",
    "website": ""
  "newAccount": "",
  "newNonce": "",
  "newOrder": "",
  "renewalInfo": "",
  "revokeCert": ""
* Connection #0 to host left intact```

Hi @xKliment, and welcome to the LE community forum :slight_smile:

You have to run that within the docker container that is running the ACME client.


Oh okay! Thats the result.

root@429939807d46:/# curl -v
* Could not resolve host:
* Closing connection 0
curl: (6) Could not resolve host:

I think there is a problem with the ports or something... because on the docker network Adguard also runs on 80 maybe etc. maybe something is blocking it

That's a DNS issue.


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