mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3840] Better support for error pages #2526
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#2526
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 @drspangle on GitHub (Jun 29, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3840
Is your feature request related to a problem? Please describe.
Right now, when a server that is being proxied via NPM isn't yet available, a 502 "bad gateway" error is returned. This is fine, it's the expected behavior, but it would be a lot nicer if it were possible to instead redirect to a nicer error page. This would be especially helpful if that page could include javascript to redirect back to the original page after a time, allowing services to come online (obviously this custom page would be written by the end user).
Describe the solution you'd like
I'd like to be able to specify the error pages for handling various errors, in particular 502. You should be able to go into a domain's settings and specify the redirection URL, and/or specify a custom static HTML file to use.
Describe alternatives you've considered
The only real alternative here is to manually edit the nginx config inside the container, which there is lots of documentation to show is possible, but that defeats the purpose of using NPM.
Additional context
@github-actions[bot] commented on GitHub (Feb 16, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍