mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2392] Letsencrypt disappearing from .conf files. / Secure Connection Failed randomly. #1686
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#1686
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 @outerregion on GitHub (Nov 11, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2392
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
The letsencrypt SSL information is being removed from the .conf file. It appears that this is happening when the check for updated certs is happening.
Nginx Proxy Manager Version
v2.9.19
To Reproduce
Steps to reproduce the behavior:
For my setup.
In my case, I have 32 .conf files.
Expected behavior
Proxyhost should load and assign the SSL to that domain.
Screenshots
Operating System
Server: ubuntu server 22.04 on a proxmox host.
Additional context
Was experiencing this on the previous version. Problem seems to only appear after a set number of proxy hosts are created. I've attached a conf file, before (1.conf.bak) and after hitting save again (1.conf). If it happened once, It could be ok, but this is happening randomly on different proxy hosts. I have substituted the domain names in the uploaded files for privacy.
1.conf.bak.txt
1.conf.txt
@qbiecom commented on GitHub (Nov 12, 2022):
Could this be the same issue as #2254?
@outerregion commented on GitHub (Nov 12, 2022):
Yup, this is a duplicate of #2254. I have implemented a brute force work around for now, but it's not really sustainable.
For posterity, the workaround is setting up a cron to backup up only files that have letsencrypt.
*/5 * * * * rsync -az /root/npm/ /root/docker/nginx-proxy-manager/data/nginx/proxy_host/ >/dev/null 2>&1
1-59/2 * * * * find . -type f -exec grep -lr "letsencrypt-acme-challenge" {} ; -exec cp -r {} /root/npm/ ; >/dev/null 2>&1