mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1709] More default site options #1272
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#1272
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 @Weilbyte on GitHub (Dec 31, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1709
Is your feature request related to a problem? Please describe.
Ability to set a proxy host as a default site, or input own default site NGINX configuration.
Describe the solution you'd like
It would be nice if a proxy host could be set as a default site so that it can catch all unknown host hits (so it could for example, work with something like https://github.com/Weilbyte/default-service). This could be in the form of a setting within the proxy host setup or an option in the "Default site" setting dialog.
Alternatively it would be okay if the "Default site" dialog had a setting that let the users input their own NGINX default site configuration.
Describe alternatives you've considered
/
Additional context
/
@inthebrilliantblue commented on GitHub (Oct 3, 2022):
This would be helpful as the "default site" settings is horribly broken if a client only connects to nginx via SSL. Want to show that 404 page? Most browsers wont even show the page via SSL because it doesnt like the self signed cert and instead show an error. And you cant even set the cert without going deep in the weeds of the container.
@github-actions[bot] commented on GitHub (Feb 28, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 13, 2025):
Issue was closed due to inactivity.