starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #3159] FIX: Operating system switch resolves DNS challenge errors #2142

New issue

Closed

opened 2026-02-26 07:34:13 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:34:13 +03:00

Owner

Originally created by @fhsevenbel on GitHub (Aug 25, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3159

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
We had a problem on our running debian machine, when requesting certificates. the errors were the same as:

We have also set up a completely new machine with debian 11 installed, same error, but a coworker of mine, tried the same on a ubuntu 22.04 machine and it worked out of the box. We were able to request working ssl certificates without any changes to the configuration.

Nginx Proxy Manager Version
2.10.4

To Reproduce
Steps to reproduce the behavior:
Non working:

set up a debian 11
install docker as stated on the official website
start a basic docker-compose like the first one on this page
try to get a certificate

Working:

same steps as above with an ubuntu os (we tried 22.04)
try to get a certificate

Expected behavior
Debian and Ubuntu should behave the same, docker is used to avoid problems like "this works on my system"

Screenshots
Sry i did not make any screenshots, but the error message is the same as in the linked issues above

Operating System
Non-working: Debian 11
Working: Ubuntu 22.04

Additional context
We were not able to use newer versions of debian and ubuntu as we were restricted to these versions

I am more than happy to help with simple debugging, as we have still servers running, with debian where sometime in the past we were able to get certificates, and we do not want to switch to another OS

Originally created by @fhsevenbel on GitHub (Aug 25, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3159  **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** We had a problem on our running debian machine, when requesting certificates. the errors were the same as: - [issue 3111](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3111) - [issue 3103](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3103) We have also set up a completely new machine with debian 11 installed, same error, but a coworker of mine, tried the same on a ubuntu 22.04 machine and it worked out of the box. We were able to request working ssl certificates without any changes to the configuration. **Nginx Proxy Manager Version** 2.10.4 **To Reproduce** Steps to reproduce the behavior: Non working: 1. set up a debian 11 2. install docker as stated on the official website 3. start a basic docker-compose [like the first one on this page](https://nginxproxymanager.com/setup/#running-the-app) 4. try to get a certificate Working: 1. same steps as above with an ubuntu os (we tried 22.04) 2. try to get a certificate **Expected behavior** Debian and Ubuntu should behave the same, docker is used to avoid problems like "this works on my system" **Screenshots** Sry i did not make any screenshots, but the error message is the same as in the linked issues above **Operating System** Non-working: Debian 11 Working: Ubuntu 22.04 **Additional context** We were not able to use newer versions of debian and ubuntu as we were restricted to these versions I am more than happy to help with simple debugging, as we have still servers running, with debian where sometime in the past we were able to get certificates, and we do not want to switch to another OS

kerem

2026-02-26 07:34:13 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:34:13 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 6, 2024):

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

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

kerem commented

2026-02-26 07:34:13 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 4, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Jun 4, 2025): Issue was closed due to inactivity.

kerem referenced this issue

2026-02-26 08:31:00 +03:00

[PR #2142] [MERGED] Bump moment from 2.27.0 to 2.29.4 in /frontend #3535

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#2142

No description provided.

Rows
Columns