-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Closed as not planned
Description
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:
- Add a new proxy host
- Set an access list
- 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.
kevinpanaro