mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 01:15:51 +03:00
[GH-ISSUE #1285] Mysql config change + Nginx restart does not apply new config #1037
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#1037
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 @rwjack on GitHub (Aug 4, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1285
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Changing settings inside the mysql database, eg. automation scripts to allow certain proxy hosts at certain times, and then reloading Nginx does not apply the setting.
Nginx Proxy Manager Version
2.9.6
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Disabling a proxy host from the DB should actually disable it on reload of nginx, not just show as disabled on the frontend UI, or I'm just not seeing an easier way of interacting with the backend using the CLI.
@chaptergy commented on GitHub (Aug 4, 2021):
This is not a bug and will not be implemented, since continuously checking the database for any changes introduces a huge computational overhead which is in no way proportional to the usefulness of this. Only NPM should modify the database.
If you want to automate things, please just use the api which unfortunately not documented, but it shouldn't be too hard to extract this information from the JSON schema and using your browsers developer console.