mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-27 02:15:51 +03:00
[GH-ISSUE #521] Proxy not working? #439
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#439
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Gershy13 on GitHub (Jul 25, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/521
Hi,
So ive had NPM working for a while now, but today it suddenly stopped working... I tried a reinstall of the container and everything but no luck... These are my issues.
When trying to get a new cert:
Failed authorization procedure. duckdns.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://.duckdns.org/.well-known/acme-challenge/UGzIv7gW9ke6k-_JTi5f2NNlb********: Timeout during connect (likely firewall problem)
(censored some of that as im not sure if its private)
And more issues:
[7/24/2020] [10:29:02 PM] [Nginx ] › ℹ info Reloading Nginx
Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0
and this (in the GUI, proxy shows as offline (red) because of this)

@BetterToAutomateTheWorld commented on GitHub (Feb 1, 2021):
I met the same issue, did you fix it ?
@github-actions[bot] commented on GitHub (Mar 27, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (May 7, 2025):
Issue was closed due to inactivity.