mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #2771] cannot login to admin interface - error create table `migrations #1905
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#1905
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 @vawaver on GitHub (Mar 29, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2771
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
After restarting the docker I found an error in log. I am not able to login to administrator menu.

Bad Gateway error.
Nginx Proxy Manager Version
v2.10.1
To Reproduce
Steps to reproduce the behavior:
[3/29/2023] [5:37:14 AM] [Global ] › ✖ error create table
migrations(idint unsigned not null auto_increment primary key,namevarchar(255),batchint,migration_timetimestamp) - ER_CANT_CREATE_TABLE: Can't create tablenginxnew.migrations(errno: 13 "Permission denied")Expected behavior
No error in the log.
Screenshots
Check the attached log file
Operating System
Ubuntu server 20.04 - latest
Additional context
@slimbeat commented on GitHub (Mar 29, 2023):
You can use following change in "docker-compose.yml" file as a work around and to login again:
image: 'jc21/mariadb-aria:10.4.15-innodbHope it helps you for now.
@vawaver commented on GitHub (Mar 29, 2023):
There is some problem, I returned to version v2.9.22
And everything is working fine.
@livealvi commented on GitHub (Mar 29, 2023):
I'm using v2.9.22 ✅
@remisharrock commented on GitHub (Mar 29, 2023):
in #2774 I give a method to check if the mysql folder permissions are ok and how to fix it.
@wokkeltje13 commented on GitHub (Mar 30, 2023):
I use an install script provided by https://github.com/tteck/Proxmox that is using SQLite, so there is no mysql that can have wrong permissions.
https://github.com/tteck/Proxmox/blob/main/install/nginxproxymanager-install.sh
No idea where I can find logfiles.
@jl-678 commented on GitHub (Mar 31, 2023):
I use the same script. Another thread here suggests that this could be a permission issue. I will check it out.
@runbgp commented on GitHub (Mar 31, 2023):
I ran into the same issue on my Docker install. Setting the app image tag to 2.9.22 allowed me to log back into the web UI.
@marcosvfc commented on GitHub (Mar 31, 2023):
Can someone try this?
@jl-678 commented on GitHub (Mar 31, 2023):
I tried again today with the same issue. Here is the log output:
@FroggMaster commented on GitHub (Apr 6, 2023):
I encountered the same error when upgrading to 2.10.2.
I've worked around the issue for now by adjusting the permissions on the npm/data/mysql folder. Changing the permissions from 755 to 777. (A few others have had success with this as mentioned in https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2774)
The problem very much does appear to be an issue with permissions relative to mysql folder.
A quick/easy workaround:
chmod 777 -R mysqlOnce the problem has been resolved the permissions can be adjusted back to 755.
If you're not keen on adjusting the permissions to 777 and I would understand why. Giving complete access to the folder is by no means secure. There is slightly more advanced and permanent workaround, documented here: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2774#issuecomment-1489466154
@github-actions[bot] commented on GitHub (Jan 24, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 10, 2025):
Issue was closed due to inactivity.