mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #218] Maintenance status page #191
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#191
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 @Unthred on GitHub (Oct 26, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/218
I am proxying my home server and I have several services I provide to my friends and family. If I am doing maintenance on my server I would like to be able to redirect them to a status page explaining what is going on and how long to expect it to continue. Seems to me this would be the perfect place to implement such a thing as all traffic to my server goes through NginxProxyManager
Here's how I think it would work. You define the location of the status page and have the ability to enable or disable it. then in each proxy host there would be an option to use that status page if its enabled. Then with a simple click of an enabled you could redirect all selected hosts to your status page informing users what is going on.
Hope that makes sense and thanks for an amazing product!
@niklas-stegmann commented on GitHub (Dec 16, 2020):
Is there any new information available about when and whether this feature will be implemented?
I like this idea!
@centralhardware commented on GitHub (Jul 29, 2021):
also interested in this feature
@Issykul commented on GitHub (Feb 27, 2023):
am also interested
@rroethof commented on GitHub (Dec 6, 2023):
also interested
@github-actions[bot] commented on GitHub (Jul 12, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@h4km4k commented on GitHub (Dec 7, 2024):
+1
@github-actions[bot] commented on GitHub (Jun 22, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍