[GH-ISSUE #8] Allow temporary disable of a proxy using checkbox #8

Closed
opened 2026-02-26 05:32:58 +03:00 by kerem · 5 comments
Owner

Originally created by @bram-pkg on GitHub (Aug 21, 2018).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/8

As the title says, a proxy or redirect should be able to be disabled using a checkbox on the edit modal.

Originally created by @bram-pkg on GitHub (Aug 21, 2018). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/8 As the title says, a proxy or redirect should be able to be disabled using a checkbox on the edit modal.
kerem 2026-02-26 05:32:58 +03:00
Author
Owner

@jc21 commented on GitHub (Aug 21, 2018):

And what should a user see in their browser when a host is disabled? The default landing page, which is a http 200, or should they get a 404 not found?

<!-- gh-comment-id:414844486 --> @jc21 commented on GitHub (Aug 21, 2018): And what should a user see in their browser when a host is disabled? The default landing page, which is a http 200, or should they get a 404 not found?
Author
Owner

@bram-pkg commented on GitHub (Aug 22, 2018):

Perhaps a default nginx 404. Or the screen you get when the proxies IP is not available.

<!-- gh-comment-id:414940874 --> @bram-pkg commented on GitHub (Aug 22, 2018): Perhaps a default nginx 404. Or the screen you get when the proxies IP is not available.
Author
Owner

@Daxx13 commented on GitHub (Dec 12, 2018):

And what should a user see in their browser when a host is disabled? The default landing page, which is a http 200, or should they get a 404 not found?

+1 to this, when disabled I think the user should see default page when no matching hostname. (same behavior as if you delete it, but without deleting of course haha)

Thanks!

<!-- gh-comment-id:446499706 --> @Daxx13 commented on GitHub (Dec 12, 2018): > > > And what should a user see in their browser when a host is disabled? The default landing page, which is a http 200, or should they get a 404 not found? +1 to this, when disabled I think the user should see default page when no matching hostname. (same behavior as if you delete it, but without deleting of course haha) Thanks!
Author
Owner

@StuFrankish commented on GitHub (Dec 29, 2018):

I'd like to up vote this one as well. Although I would opt for a global configuration setting that would let you choose what response code to return when a site is disabled - Not Found, Service Unavailable etc...

Just to add to this though - Having the toggle either in the modal or the menu as well as having the "Enabled" status shown on the table list as well, and the dashboard to show the total hosts with an additional number of disabled hosts (if any)

<!-- gh-comment-id:450448344 --> @StuFrankish commented on GitHub (Dec 29, 2018): I'd like to up vote this one as well. Although I would opt for a global configuration setting that would let you choose what response code to return when a site is disabled - Not Found, Service Unavailable etc... Just to add to this though - Having the toggle either in the modal or the menu as well as having the "Enabled" status shown on the table list as well, and the dashboard to show the total hosts with an additional number of disabled hosts (if any)
Author
Owner

@jc21 commented on GitHub (Jan 4, 2019):

Added in v2.0.8.

<!-- gh-comment-id:451363511 --> @jc21 commented on GitHub (Jan 4, 2019): Added in v2.0.8.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#8
No description provided.