mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2990] migrations_lock database error, stuck on login page #2039
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#2039
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 @SteinMalte on GitHub (Jun 8, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2990
Hello,
I have an issue with my nginxproxymanager instance that I used for a couple of months.
One day I wanted to visist my grafana dashbaord but I was not forwarded. I found that my nginxproxymanager instance is unusable because of the following error that keeps me stuck on the login page of NPM with the "Bad Gateway" notification as shown in the screenshot below.
By the way this is my database log, as you can see I use the jc21/mariadb:latest image as intended by the docker-compose file on the official website.
Basically I did not change anything manually, all of my updates are performed by watchtower.
I hope there is a way to recover my database so that I do not have to reconfigure eveyting.
Regards, Malte
@centralhardware commented on GitHub (Jul 1, 2023):
any solution? certificates are expiring, and it's no way to update them, due this error
@SteinMalte commented on GitHub (Jul 1, 2023):
Yeah kind of, I switched the jc21/mariadb-aria:latest image for the offical mariadb:latest image in the docker-compose.yml and at at least it seems to be working at the moment my settings are not gone but it does not feel safe. On top of that it is throwing warnings as soon as someone tries to access nginxproxymanager so I really do not feel very good about this solution.
What I have found is that the installation manual on the NPM website seems like using a database was optional but I dont know if that is correct and havent tried without yet. Id advise you to use the mariadb image fix like I did and save your settings in case something does break forever.
@nmatton commented on GitHub (Aug 22, 2023):
this fix also works for me, but as you said, probably not the cleaner one
@github-actions[bot] commented on GitHub (Apr 11, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Jun 8, 2025):
Issue was closed due to inactivity.