mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #1846] Let's Encrypt not working #1356
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#1356
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 @DNAScanner on GitHub (Feb 11, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1846
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
For a few days now I'm trying to get my let's encrypt SSL to work, but it doesn't, and I don't know why
Nginx Proxy Manager Version
v2.9.15
To Reproduce
Steps to reproduce the behavior:
Domain Names: 'dnascanner.dynv6.net'
Scheme: http
Forward Hostname/IP: raspberrypi
Forward Port: 8080
Every switch off (cache assets, block common exploits, websockets support)
Expected behavior
I expected, that I get the SSL on my webserver working
Screenshots
https://cdn.discordapp.com/attachments/910203843625766922/941733175552524388/unknown.png
Operating System
Running on RaspberryPi 4b 'raspberrypi os'
Additional context
Docker Version: 20.10.12, build e91ed57
Browser Version: OperaGX LVL3 (core 83.0.4254.46)
Let's Encrypt Report: https://cdn.discordapp.com/attachments/910203843625766922/941735452891832432/log.log
@einlichtvogel commented on GitHub (Feb 11, 2022):
Same here 👋🏼
@einlichtvogel commented on GitHub (Feb 11, 2022):
I just found out, if you create it over the "certificate" tab it works, but only if your website does not respond with a 500
@DNAScanner commented on GitHub (Feb 11, 2022):
For me it still doesn't work..
@Skizz83 commented on GitHub (Feb 13, 2022):
Same here too, exactly the same error message in the logs
@anthonyb800 commented on GitHub (Feb 13, 2022):
Same issue & same error here when trying to get a wildcard cert w/Cloudflare API.
@einlichtvogel commented on GitHub (Feb 13, 2022):
Now it is working fine for me, I installed it on Proxmox with the Third-Party script, without docker on an Alpine container. It only throws an exception when the website throws an 500 html code.
@DNAScanner commented on GitHub (Feb 13, 2022):
How tf did u do that? Could u send me a link or some intructions or smt?
@einlichtvogel commented on GitHub (Feb 13, 2022):
https://github.com/ej52/proxmox-scripts/tree/main/lxc/nginx-proxy-manager linked under https://nginxproxymanager.com/third-party/ @DNAScanner
@anthonyb800 commented on GitHub (Feb 13, 2022):
Looks like it worked for me this morning. Not sure what changed, but I obtained the cert with no issues
@HerrFrutti commented on GitHub (Feb 13, 2022):
same. reverting back to version 2.9.10 does it for me.
running on a pi 4 4gb ram
Raspbian GNU/Linux 11 (bullseye)
@rrreid commented on GitHub (Feb 20, 2022):
I was getting the same 'Internal Error' issue, but once I restarted npm, it loaded back up with the updated cert. All seems to be working as expected now.
@github-actions[bot] commented on GitHub (Feb 24, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Dec 1, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Dec 5, 2025):
Issue was closed due to inactivity.