mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #226] Cannot generate letsencrypt certificate "Internal Error" #198
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#198
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 @dbrosy on GitHub (Nov 2, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/226
Ok I don't understand why this doesn't work.
I have created nginx proxy manager with 80, 81 and 443 open to public. I am trying to secure dashboard on port 81 with proxy.<example.com> (<example.com> not my real domain)
I can browse to http(s)://proxy.example.com and see login page.
If I try to create an ssl cert for my domain i get "internal error" with following in logs:
docker-compose.yml:
config.json
The error seems to be related to /.well-known/acme-challenge/...
What am I doing wrong?
I would like to the create certs for any domain I point to my proxy
@dbrosy commented on GitHub (Nov 7, 2019):
ok after looking at this for days it looks like my gateway / firewall is causing issue
@dbrosy commented on GitHub (Nov 7, 2019):
Just an update, I discovered it was caused by a qnap NAS using upnp on 80 and 443.
@emass-sec commented on GitHub (Jan 1, 2020):
Same, I turned off port 80 on my firewall recently and then connected the dots that's why I couldn't generate LetsEncrypt certificates in NPM anymore. Opened port 80 to NPM server again, and bam, able to generate certs again. Anyone know why it needs port 80?