NginxProxyManager / NginxProxyManager/nginx-proxy-manager

[Bug] Syntax error in Advanced config silently deletes .conf file, UI still shows "Online"

Open
#5,735 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

[Bug] Syntax error in Advanced config silently deletes .conf file, UI still shows "Online"
Version: 2.15.1
Steps to reproduce:
Create a proxy host with valid settings, save successfully
Edit the proxy host, go to "Advanced" tab
Add an invalid nginx directive, e.g. proxy_passs http://127.0.0.1:8080; (typo)
Click "Save"
Expected behavior:
UI should show an error message indicating the config is invalid
Actual behavior:
UI shows "Save successful" / proxy host still shows "Online" ✅
The .conf file (e.g. /data/nginx/proxy_host/3.conf) is silently deleted ❌
The proxy stops working with no indication ❌
Running nginx -t afterwards passes (because the broken file is already gone)
No error is shown in the UI, no toast notification, no status change
Impact:
The proxy silently fails with zero notification
Users cannot detect the failure without manually checking file existence or external monitoring
This has been the behavior since the framework rewrite (v2.13+)
Suggested fix:
Propagate the error to the API response so the frontend can display it
Roll back the database state or mark the proxy host as "error" in the UI
Environment:
Docker: jc21/nginx-proxy-manager:2.15.1
OS: [centos 7.9 ]
Docker version: [Docker version 26.1.2]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the proxy-host save flow from the Advanced tab and trace how an invalid nginx directive reaches the API response and file generation for /data/nginx/proxy_host/3.conf. Reproduce the issue, then verify that the invalid configuration produces a visible UI error, preserves or marks the proxy-host state appropriately, and does not silently delete the .conf file.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, nginx
Domain
api, backend, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.