[GH-ISSUE #105] Errors when using seperate MYSQL server #93

Closed
opened 2026-02-26 05:34:21 +03:00 by kerem · 4 comments
Owner

Originally created by @danmed on GitHub (Mar 15, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/105

migration failed with error: create table auth (idint unsigned not null auto_increment primary key,created_ondatetime not null,modified_ondatetime not null,user_idint unsigned not null,typevarchar(30) not null,secretvarchar(255) not null,metajson not null,is_deletedint unsigned not null default '0') - ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'json not null,is_deleted int unsigned not null default '0')' at line 1

This occurs when it first tries to create the database.. only 2 tables are created :

migrations
migrations_lock

Originally created by @danmed on GitHub (Mar 15, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/105 `migration failed with error: create table `auth` (`id` int unsigned not null auto_increment primary key, `created_on` datetime not null, `modified_on` datetime not null, `user_id` int unsigned not null, `type` varchar(30) not null, `secret` varchar(255) not null, `meta` json not null, `is_deleted` int unsigned not null default '0') - ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'json not null, `is_deleted` int unsigned not null default '0')' at line 1` This occurs when it first tries to create the database.. only 2 tables are created : migrations migrations_lock
kerem closed this issue 2026-02-26 05:34:21 +03:00
Author
Owner

@danmed commented on GitHub (Mar 15, 2019):

fixed by updating MySQL to MariaDB and using MySQL as the engine in the config.json

<!-- gh-comment-id:473292707 --> @danmed commented on GitHub (Mar 15, 2019): fixed by updating MySQL to MariaDB and using MySQL as the engine in the config.json
Author
Owner

@jc21 commented on GitHub (Mar 18, 2019):

For anyone coming across this in future, only MySQL server v5.7.8 and above, and MariaDB databases are supported with this project.

<!-- gh-comment-id:473736569 --> @jc21 commented on GitHub (Mar 18, 2019): For anyone coming across this in future, only MySQL server v5.7.8 and above, and MariaDB databases are supported with this project.
Author
Owner

@dgancedo commented on GitHub (Apr 26, 2019):

I'm having the same issue with a fresh install but I'm using MariaDB 10 on other container
Server version: 10.1.38-MariaDB-0ubuntu0.18.04.1 Ubuntu 18.04

the error is:
writing new private key to '/data/nginx/dummykey.pem'

Complete
[4/26/2019] [11:41:01 PM] [Migrate ] › ℹ info Current database version: none
[4/26/2019] [11:41:01 PM] [Migrate ] › ℹ info [initial-schema] Migrating Up...
migration file "20190227065017_settings.js" failed
migration failed with error: create table auth (id int unsigned not null auto_increment primary key, created_on datetime not null, modified_on datetime not null, user_id int unsigned not null, type varchar(30) not null, secret varchar(255) not null, meta json not null, is_deleted int unsigned not null default '0') - ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'json not null, is_deleted int unsigned not null default '0')' at line 1

and the last part keep repeating, any idea?

<!-- gh-comment-id:487234130 --> @dgancedo commented on GitHub (Apr 26, 2019): I'm having the same issue with a fresh install but I'm using MariaDB 10 on other container Server version: 10.1.38-MariaDB-0ubuntu0.18.04.1 Ubuntu 18.04 the error is: writing new private key to '/data/nginx/dummykey.pem' ----- Complete [4/26/2019] [11:41:01 PM] [Migrate ] › ℹ info Current database version: none [4/26/2019] [11:41:01 PM] [Migrate ] › ℹ info [initial-schema] Migrating Up... migration file "20190227065017_settings.js" failed migration failed with error: create table `auth` (`id` int unsigned not null auto_increment primary key, `created_on` datetime not null, `modified_on` datetime not null, `user_id` int unsigned not null, `type` varchar(30) not null, `secret` varchar(255) not null, `meta` json not null, `is_deleted` int unsigned not null default '0') - ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'json not null, `is_deleted` int unsigned not null default '0')' at line 1 and the last part keep repeating, any idea?
Author
Owner

@jc21 commented on GitHub (Apr 27, 2019):

With Mariadb, the JSON field type was introduced in 10.2.7.

<!-- gh-comment-id:487237326 --> @jc21 commented on GitHub (Apr 27, 2019): With Mariadb, the JSON field type [was introduced in 10.2.7](https://mariadb.com/kb/en/library/json-data-type/).
Sign in to join this conversation.
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#93
No description provided.