mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #816] Default ssl on a custom domain for the admin panel #690
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#690
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 @theRAGEhero on GitHub (Jan 9, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/816
Hello and thank you for your awesome job.
I was wondering if it's possible to have the admin panel on SSL just after the docker-compose installation.
I was thinking it in this way: I add a domain in the docker-compose file. That domain is going to be used for the admin panel (instead of port 81).
Once that the installation is complete, npm asks for an SSL certificate on that domain.
If the domain is not written in the .yml file, then npm use the port 81 by default.
Maybe it's a stupid idea, but maybe no.
Thank you again!
@chaptergy commented on GitHub (May 12, 2021):
I'll mark this as a duplicate of https://github.com/jc21/nginx-proxy-manager/issues/182, since it generally is. Your specific request to set the data in the docker-compose file could be a comment over there.