[GH-ISSUE #181] Startup errors #158

New issue

Closed

opened 2026-02-26 06:30:55 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:30:55 +03:00

Owner

Originally created by @gurumark on GitHub (Aug 3, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/181

I get the following error when starting up nginx-proxy container:

migration file "20190227065017_settings.js" failed
migration failed with error: alter table setting add primary key setting_pkey(id) - ER_TOO_LONG_KEY: Specified key was too long; max key length is 1000 bytes
[8/3/2019] [2:42:41 AM] [Global ] › ✖ error alter table setting add primary key setting_pkey(id) - ER_TOO_LONG_KEY: Specified key was too long; max key length is 1000 bytes
[8/3/2019] [2:42:42 AM] [Migrate ] › ℹ info Current database version: 20190218060101
[8/3/2019] [2:42:42 AM] [Migrate ] › ℹ info [settings] Migrating Up...
migration file "20190227065017_settings.js" failed
migration failed with error: create table setting (id varchar(255) not null, name varchar(100) not null, description varchar(255) not null, value varchar(255) not null, meta json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists

It seems like it is trying to insert a key which is too long to settings table.

Originally created by @gurumark on GitHub (Aug 3, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/181 I get the following error when starting up nginx-proxy container: migration file "20190227065017_settings.js" failed migration failed with error: alter table `setting` add primary key `setting_pkey`(`id`) - ER_TOO_LONG_KEY: Specified key was too long; max key length is 1000 bytes [8/3/2019] [2:42:41 AM] [Global ] › ✖ error alter table `setting` add primary key `setting_pkey`(`id`) - ER_TOO_LONG_KEY: Specified key was too long; max key length is 1000 bytes [8/3/2019] [2:42:42 AM] [Migrate ] › ℹ info Current database version: 20190218060101 [8/3/2019] [2:42:42 AM] [Migrate ] › ℹ info [settings] Migrating Up... migration file "20190227065017_settings.js" failed migration failed with error: create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists It seems like it is trying to insert a key which is too long to settings table.

kerem closed this issue

2026-02-26 06:30:55 +03:00

kerem commented

2026-02-26 06:30:56 +03:00

Author

Owner

@gurumark commented on GitHub (Aug 3, 2019):

To get it working again, I altered the primary key column to text. It started giving the following:

[8/3/2019] [3:09:13 AM] [Migrate ] › ℹ info Current database version: 20190218060101
[8/3/2019] [3:09:13 AM] [Migrate ] › ℹ info [settings] Migrating Up...
migration file "20190227065017_settings.js" failed
migration failed with error: create table setting (id varchar(255) not null, name varchar(100) not null, description varchar(255) not null, value varchar(255) not null, meta json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists
[8/3/2019] [3:09:13 AM] [Global ] › ✖ error create table setting (id varchar(255) not null, name varchar(100) not null, description varchar(255) not null, value varchar(255) not null, meta json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists

I drop the setting table then it recreates and gives the same error.

@gurumark commented on GitHub (Aug 3, 2019): To get it working again, I altered the primary key column to text. It started giving the following: [8/3/2019] [3:09:13 AM] [Migrate ] › ℹ info Current database version: 20190218060101 [8/3/2019] [3:09:13 AM] [Migrate ] › ℹ info [settings] Migrating Up... migration file "20190227065017_settings.js" failed migration failed with error: create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists [8/3/2019] [3:09:13 AM] [Global ] › ✖ error create table `setting` (`id` varchar(255) not null, `name` varchar(100) not null, `description` varchar(255) not null, `value` varchar(255) not null, `meta` json not null) - ER_TABLE_EXISTS_ERROR: Table 'setting' already exists I drop the setting table then it recreates and gives the same error.

kerem commented

2026-02-26 06:30:56 +03:00

Author

Owner

@macf0x commented on GitHub (Oct 13, 2019):

See this link. Older version of mariadb isn't supported

https://github.com/jc21/nginx-proxy-manager/issues/146#issuecomment-533845196

@macf0x commented on GitHub (Oct 13, 2019): See this link. Older version of mariadb isn't supported https://github.com/jc21/nginx-proxy-manager/issues/146#issuecomment-533845196

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#158

No description provided.

Rows
Columns