[GH-ISSUE #4415] Certbot fails when host has only IPv6 and no IPv4 address #2825

New issue

Open

opened 2026-02-26 07:36:54 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 07:36:54 +03:00

Owner

Originally created by @pzauner on GitHub (Mar 4, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4415

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker 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
Certbot will fail when requesting a new ssl certificate, if you only have an IPv6-address. If you run certbot on the host, you will get a ssl cert just fine.

Nginx Proxy Manager Version
v2.12.3

To Reproduce
Steps to reproduce the behavior:

Have a server without an IPv4 address (e.g. one from v6node.com).
Install NPM.
Make sure your AAAA record is correctly set and propagated for your domain. (A records? Where we are going, we don't need A records...)
In NPM: request new ssl cert for your domain and accept TOS.
Admire error page:
`debug log to /tmp/letsencrypt-log/letsencrypt.log
An unexpected error occurred:
ValueError: Requesting acme-v02.api.letsencrypt.org/directory: Network is unreachable
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:518:28)
at maybeClose (node:internal/child_process:1104:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)`

If you add an IPv4-address however, it just runs fine... Also runs fine on host without IPv4, just not via docker.

Expected behavior
Add new ssl cert to the list.

Operating System
Debian, x86

Originally created by @pzauner on GitHub (Mar 4, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4415 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker 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** Certbot will fail when requesting a new ssl certificate, if you only have an IPv6-address. If you run certbot on the host, you will get a ssl cert just fine. **Nginx Proxy Manager Version** v2.12.3 **To Reproduce** Steps to reproduce the behavior: 1. Have a server without an IPv4 address (e.g. one from v6node.com). 2. Install NPM. 3. Make sure your AAAA record is correctly set and propagated for your domain. (A records? Where we are going, we don't need A records...) 4. In NPM: request new ssl cert for your domain and accept TOS. 5. Admire error page: `debug log to /tmp/letsencrypt-log/letsencrypt.log An unexpected error occurred: ValueError: Requesting acme-v02.api.letsencrypt.org/directory: Network is unreachable 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:518:28) at maybeClose (node:internal/child_process:1104:16) at ChildProcess._handle.onexit (node:internal/child_process:304:5)` If you add an IPv4-address however, it just runs fine... Also runs fine on host without IPv4, just not via docker. **Expected behavior** Add new ssl cert to the list. **Operating System** Debian, x86

kerem added the

stale

bug

labels

2026-02-26 07:36:54 +03:00

kerem commented

2026-02-26 07:36:55 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 23, 2025):

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

@github-actions[bot] commented on GitHub (Sep 23, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#2825

No description provided.

Rows
Columns