mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #2261] [enhancement|feature request] Add redirect option for access lists. #1609
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#1609
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 @TheRealVira on GitHub (Sep 12, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2261
Currently, whenever someone wants to access a host and doesn't meet its' dedicated access list requirements they receive a 403 forbidden error message. This may be fine for many, but I'd like to redirect the user to my default page instead. I'd imagine it to be similar to the "Default Site" setting.
@the1ts commented on GitHub (Sep 12, 2022):
@TheRealVira I would say use the optional custom http_top.conf as described here
perhaps the below will work:
error_page 403 http://google.com;@TheRealVira commented on GitHub (Sep 12, 2022):
Yup this works for me. Thanks for the quick reply @the1ts ! I guess if you really want different redirects depending on which access list you use you'd need to use different configs. But I am okay with just my one default page.