Commit 08b5160
authored
Fix host enable/disable functionality - Use NPM native endpoints
- Fixed critical bug where --host-disable showed 'disabled' in UI but sites remained accessible
- Replaced generic PUT /api/nginx/proxy-hosts/{id} approach with NPM's dedicated endpoints:
• POST /api/nginx/proxy-hosts/{id}/enable for enabling hosts
• POST /api/nginx/proxy-hosts/{id}/disable for disabling hosts
- Discovered through browser dev tools inspection of NPM web interface requests
- Added comprehensive documentation explaining the bug discovery process
- Removed debug output messages for cleaner user experience
The generic JSON modification approach only updates the UI status but doesn't
actually disable network access. NPM's native endpoints properly handle the
nginx configuration changes required for actual functionality.
Resolves: GitHub issue #181 parent 430ede0 commit 08b5160
1 file changed
+1
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
9 | | - | |
| 9 | + | |
10 | 10 | | |
11 | 11 | | |
12 | 12 | | |
| |||
0 commit comments