NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Let's Encrypt not submitting data
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?- Yes
- Are you sure you're not using someone else's docker image?
- Yes
- Have you searched for similar issues (both open and closed)?
- Yes
Describe the bug
https://community.letsencrypt.org/t/internal-error-nginx-proxy-manager/230270
- Yes
Nginx Proxy Manager Version
v2.12.1
To Reproduce
Steps to reproduce the behavior:
Submit the LetsEncrypt information after entering the password and Username for DDNS service such as afraid.org.
Expected behavior
Creation of SSL certicate
Error:
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')': /packages/0e/f8/87fe7a3f8ef01b13218939ec69e7da5f2e1eb1578df43ff7101ba0637cb5/certbot_dns_freedns-0.1.0-py2.py3-none-any.whl.metadata
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')': /packages/0e/f8/87fe7a3f8ef01b13218939ec69e7da5f2e1eb1578df43ff7101ba0637cb5/certbot_dns_freedns-0.1.0-py2.py3-none-any.whl.metadata
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')': /packages/0e/f8/87fe7a3f8ef01b13218939ec69e7da5f2e1eb1578df43ff7101ba0637cb5/certbot_dns_freedns-0.1.0-py2.py3-none-any.whl.metadata
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')': /packages/0e/f8/87fe7a3f8ef01b13218939ec69e7da5f2e1eb1578df43ff7101ba0637cb5/certbot_dns_freedns-0.1.0-py2.py3-none-any.whl.metadata
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')': /packages/0e/f8/87fe7a3f8ef01b13218939ec69e7da5f2e1eb1578df43ff7101ba0637cb5/certbot_dns_freedns-0.1.0-py2.py3-none-any.whl.metadata
ERROR: Could not install packages due to an OSError: HTTPSConnectionPool(host='files.pythonhosted.org', port=443): Max retries exceeded with url: /packages/0e/f8/87fe7a3f8ef01b13218939ec69e7da5f2e1eb1578df43ff7101ba0637cb5/certbot_dns_freedns-0.1.0-py2.py3-none-any.whl.metadata (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: pip install --upgrade pip
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)
Domain Names *
*.spehr.ignorelist.com
Operating System
Docker, Ubuntu 22.04
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failure reported at /app/lib/utils.js and reproduce the Let's Encrypt submission using the jc21/nginx-proxy-manager:latest Docker image and the freedns Certbot package. Investigate the reported name-resolution and package-installation failure; done means the stated DDNS flow can create an SSL certificate successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, node.js, python, typescript
- Domain
- devops, infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100