mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #764] Custom page if service is offline. #647
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#647
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 @scolastico on GitHub (Dec 7, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/764
Is your feature request related to a problem? Please describe.
I would find it nice if there is a setting like the "default page" for services what are currently offline.
Describe the solution you'd like
Look above.
Describe alternatives you've considered
i can't think of any alternatives
Additional context
nothing to show here
@osnet commented on GitHub (Dec 9, 2020):
in this case the npm should have to test for status codes like 20x, 40x or 50x mmmh
too much stuff to do
it would be easier to edit the systemwide proxy settings with static error pages this would cover your issue
@osnet commented on GitHub (Dec 9, 2020):
but ... if you mean a static page is npm is ofline ? maybe a load "balancer" setup that redirects everything to a static nginx page if host xy is offline ? : )
@scolastico commented on GitHub (Jan 7, 2021):
What could work is a alternate error page in the nginx settings.
https://serverfault.com/questions/426347/nginx-reverse-proxy-error-page
@github-actions[bot] commented on GitHub (Mar 22, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (May 2, 2025):
Issue was closed due to inactivity.