NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Issue Database - Filsystem mismatch
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Hello,
I found an issue I caused myself somehow during workiing woth Proxymanager.
In the log file, I consistently saw the message: "conflicting server name ******* on [::]:80, ignored." Even after deleting all configurations for this subdomain in the web UI, the message persisted, and Certbot frequently failed.
The root cause was a lingering 1.conf configuration file in redirection_host from an earlier attempt, despite there being no redirection configured in the UI.
To prevent this for other users, I suggest implementing a check to clear configuration files that exist on the filesystem but are no longer present in the database.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by tracing how the redirection_host configuration and its 1.conf file are created and removed, then compare that with the database state represented in the web UI. Done should prevent filesystem configuration left from an earlier attempt from persisting after the corresponding database entry is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100