mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #1115] error create table migrations (id int unsigned not null auto_increment primary key, name varchar(255), batch int, migration_time timestamp) - ER_TABLESPACE_EXISTS: Tablespace for table 'npm.migrations' exists. Please … #917
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#917
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 @Roei639 on GitHub (May 21, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1115
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
The log returns an error and cannot be connected to the management interface
error create table
migrations(idint unsigned not null auto_increment primary key,namevarchar(255),batchint,migration_timetimestamp) - ER_TABLESPACE_EXISTS: Tablespace for table 'npm.migrations' exists. Please DISCARD the tablespace before IMPORTNginx Proxy Manager Version
2.9.3
To Reproduce
Steps to reproduce the behavior:
4. See error
Expected behavior
Screenshots
Operating System
Ubuntu 20.04.2
Additional context
Installed in Docker
@shaulliv commented on GitHub (Apr 14, 2023):
I had this issue with docker, a restart of the DB container fixed it.
@cgraj04 commented on GitHub (May 7, 2023):
is this resolved yet, am also facing the same issue
@mateuscmtropical commented on GitHub (Jul 6, 2023):
One of the solutions that may work is to restart the DB container.
Another one of my cases, the volume was corrupted/dirty so I deleted it and did the docker build/up again.
@xela1601 commented on GitHub (Nov 8, 2023):
I also have this error. restarting the database did not help. I dont want to delete the volume, because i don't have it backed up.
@pthoelken commented on GitHub (Nov 17, 2023):
For your workaround you have to set the permissions manually by this script for example. Save this as startup_npm.sh in your folder from docker-compose.yml file.
@wufei0 commented on GitHub (Feb 29, 2024):
this solved my problem.
@pthoelken commented on GitHub (Feb 29, 2024):
I can't get, why this is not fixed till now in the base image.
@github-actions[bot] commented on GitHub (Oct 12, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Oct 15, 2025):
Issue was closed due to inactivity.