mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #3899] Unable to log in after upgrading from 2.11.2 to 2.11.3 #2558
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2558
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wxyShine on GitHub (Jul 26, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3899
2.11.2 has been working fine, but after updating to 2.11.3, it's not working.
@wxyShine commented on GitHub (Jul 26, 2024):
#1769 It looks the same as this one.
@Mariyo commented on GitHub (Aug 2, 2024):
Same for me, unfortunately downgrade even to 2.10 does not help. Snapshot from docker logs:
@wxyShine commented on GitHub (Aug 3, 2024):
I chose to delete the existing one and reinstalled it
@CosinusJay commented on GitHub (Aug 10, 2024):
I have the same problem right now, reinstalling did not fix it :(
Are there any external directories and or configs outside of the docker compose directory that i need to remove?
@CosinusJay commented on GitHub (Aug 10, 2024):
Nevermind, i deleted the folders but not the containers 🤦🏻♂️
@Mariyo commented on GitHub (Aug 22, 2024):
I had to reinstall it too and decided to:
:latesttag to exact onesimage: 'jc21/nginx-proxy-manager:2.11.3'sqlitedatabasedataandletsencryptfoldersLets hope it will help me to manage next upgrades more carefully so I can revert easily in similar case 🤞
@wxyShine commented on GitHub (Dec 2, 2024):
v2.12.1 also has this problem after a short time of normal use, Request a solution
@wxyShine commented on GitHub (Dec 2, 2024):
compose.yml@github-actions[bot] commented on GitHub (Jun 30, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍