[GH-ISSUE #1753] proxy_host/*.conf files sometimes inconsistent with UI #1305

Closed
opened 2026-02-26 06:36:38 +03:00 by kerem · 2 comments
Owner

Originally created by @eitch on GitHub (Jan 12, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1753

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug

  • When i check the proxy_host/*.conf file i saw that for instance sometimes TLS was not enabled, even though it was enabled in the UI.
  • After saving the proxy host configuration in the UI it got updated
  • But this then sometimes lead to other corruptions. I.e. I'm proxying the manager itself, so it isn't accessible at port 81 and then sometimes its TLS configuration gets lost and i loose access to the UI. I then need to enable port 81 again, fix the configuration, after which i can then disable port 81 again.

And while we are here: An auto focus on the login form's username would be splendid!

Nginx Proxy Manager Version
v2.9.14

To Reproduce
Steps to reproduce the behavior:

  1. Add a new proxy host
  2. Set an access list
  3. Modify the access list after the fact

Or do some other changes

Expected behavior
The configuration files must always be consistent with the UI

Screenshots
None available at the moment

Operating System
Ubuntu VM

Additional context
n.a.

Originally created by @eitch on GitHub (Jan 12, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1753 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** * When i check the proxy_host/*.conf file i saw that for instance sometimes TLS was not enabled, even though it was enabled in the UI. * After saving the proxy host configuration in the UI it got updated * But this then sometimes lead to other corruptions. I.e. I'm proxying the manager itself, so it isn't accessible at port 81 and then sometimes its TLS configuration gets lost and i loose access to the UI. I then need to enable port 81 again, fix the configuration, after which i can then disable port 81 again. And while we are here: An auto focus on the login form's username would be splendid! **Nginx Proxy Manager Version** v2.9.14 **To Reproduce** Steps to reproduce the behavior: 1. Add a new proxy host 2. Set an access list 3. Modify the access list after the fact Or do some other changes **Expected behavior** The configuration files must always be consistent with the UI **Screenshots** None available at the moment **Operating System** Ubuntu VM **Additional context** n.a.
kerem 2026-02-26 06:36:38 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@github-actions[bot] commented on GitHub (Feb 27, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:1965643939 --> @github-actions[bot] commented on GitHub (Feb 27, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Apr 12, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2798385433 --> @github-actions[bot] commented on GitHub (Apr 12, 2025): Issue was closed due to inactivity.
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#1305
No description provided.