mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #4575] Features to add from a first time user #2924
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#2924
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 @n3gwg on GitHub (Jun 11, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4575
Enhancement 1 - environment variables to be used for initial setup in docker compose file, they could be ignored if the initial configuration file exists upon starting the container.
admin_passwsord=blah
or
admin_password_has=hash
admin_email='admin@mydomain.com'
Enhancement 2 - healthcheck script
Are there any plans to have a health check script within the container?
Granted a long cmd using curl (presuming the container is inclusive of the curl binary) and such could be created in the docker compose healthcheck section, but adding a health check script that tests that everything is running on the ports would be nice.
Enhancement 3 - usernames
How hard would it be to add a username to the database, thus offering the user the ability to login either with their user or alternatively with their email address?
Stuart
@github-actions[bot] commented on GitHub (Dec 11, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍