mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #413] lets encrypt "internal error" / connectivity issue? #348
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#348
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 @anthonymobile on GitHub (May 19, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/413
after a flawless working install i started having problems a few weeks ago with adding new proxy hosts getting the "internal error" popup. i ignored it. then i noticed others reporting it, so wondering if this is related to #396.
after trying clean installs (blow away all images, containers and config) and even installing older images from a month or so ago still can't avoid the dreaded "internal error"
the one variable has been the addition of a pihole on my network. but i've removed that entirely and reset the DNS pointer on my router and still same behavior.
this -looks- like a connectivity error and normally i would not file a bug report, but nothing has changed on my setup (except the pihole which i removed). if it obviously is please close and i'll continue troubleshooting.
Describe the bug
To Reproduce
Steps to reproduce the behavior:
/var/log/letsencrypt.log
Operating System
@anthonymobile commented on GitHub (May 19, 2020):
never mind, it is a connectivity issue.