mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1804] Do not write /etc/letsencrypt/credentials contents to log #1333
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#1333
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 @olivergrahl on GitHub (Jan 25, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1804
After setting up a Letsencrypt SSL certificate using a Google DNS challenge, the credentials provided as "Credentials File Content" get written to the log in plain text.
My suggestion would be to either not log this step at all, or at least strip the private_key from the log output.
I think it's risky enough to store the credentials in the db. Let's not also write it to the log. Thx for considering!
github.com/NginxProxyManager/nginx-proxy-manager@1f3ac7a9ec/backend/internal/certificate.js (L906)@github-actions[bot] commented on GitHub (Feb 25, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 10, 2025):
Issue was closed due to inactivity.