nginx-proxy-manager icon indicating copy to clipboard operation
nginx-proxy-manager copied to clipboard

No matching distribution found for certbot-dns-duckdns~=1.0

Open Ajaymamtora opened this issue 1 year ago • 1 comments

CommandError: WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/certbot-dns-duckdns/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/certbot-dns-duckdns/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/certbot-dns-duckdns/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/certbot-dns-duckdns/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/certbot-dns-duckdns/
ERROR: Could not find a version that satisfies the requirement certbot-dns-duckdns~=1.0 (from versions: none)
ERROR: No matching distribution found for certbot-dns-duckdns~=1.0

    at /app/lib/utils.js:16:13
    at ChildProcess.exithandler (node:child_process:430:5)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5)

Ajaymamtora avatar Sep 22 '24 22:09 Ajaymamtora

This was a problem for me where the docker container didn't have access to the internet. I had to enable ipv4 forwarding on the host, then restart docker to resolve.

sysctl -w net.ipv4.ip_forward=1 sudo service docker restart

tonym128 avatar Oct 19 '24 22:10 tonym128

I might have a similar issue:

CommandError: Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

    at /app/lib/utils.js:16:13
    at ChildProcess.exithandler (node:child_process:430:5)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at Socket. (node:internal/child_process:457:11)
    at Socket.emit (node:events:519:28)
    at Pipe. (node:net:339:12)

UP:

CasaOS caused an issue with the database I think. I re-installed the container.

Then there was another issue with DNS. Today I bought a domain and used Cloudflare instead. I had to set 120 Propagation Seconds to see the SSL challenge pass.

DuckDNS is unreliable.

alexsmedile avatar Oct 22 '24 23:10 alexsmedile

Issue is now considered stale. If you want to keep it open, please comment :+1:

github-actions[bot] avatar May 17 '25 02:05 github-actions[bot]