starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #502] migration failed with error: show fields from proxy_host where field = 'forward_ip' #429

New issue
Closed
opened 2026-02-26 06:32:49 +03:00 by kerem · 3 comments
kerem commented 2026-02-26 06:32:49 +03:00
Owner
Copy link

Originally created by @ThomLS on GitHub (Jul 12, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/502

I'm receving the following error while doing the normal set-up of NGINX proxy manager.

migration failed with error: show fields from proxy_host where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only

[7/12/2020] [3:34:14 PM] [Global ] › ✖ error show fields from proxy_host where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only

[7/12/2020] [3:34:15 PM] [Migrate ] › ℹ info Current database version: 20180929054513

[7/12/2020] [3:34:15 PM] [Migrate ] › ℹ info [forward_host] Migrating Up...

migration file "20181019052346_forward_host.js" failed

migration failed with error: show fields from proxy_host where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only

[7/12/2020] [3:34:15 PM] [Global ] › ✖ error show fields from proxy_host where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only

[7/12/2020] [3:34:16 PM] [Migrate ] › ℹ info Current database version: 20180929054513

[7/12/2020] [3:34:16 PM] [Migrate ] › ℹ info [forward_host] Migrating Up...

migration file "20181019052346_forward_host.js" failed

migration failed with error: show fields from proxy_host where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only

[7/12/2020] [3:34:16 PM] [Global ] › ✖ error show fields from proxy_host where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only

[7/12/2020] [3:34:17 PM] [Migrate ] › ℹ info Current database version: 20180929054513

[7/12/2020] [3:34:17 PM] [Migrate ] › ℹ info [forward_host] Migrating Up...

migration file "20181019052346_forward_host.js" failed

migration failed with error: show fields from proxy_host where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only

Originally created by @ThomLS on GitHub (Jul 12, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/502 I'm receving the following error while doing the normal set-up of NGINX proxy manager. migration failed with error: show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only [7/12/2020] [3:34:14 PM] [Global ] › ✖ error show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only [7/12/2020] [3:34:15 PM] [Migrate ] › ℹ info Current database version: 20180929054513 [7/12/2020] [3:34:15 PM] [Migrate ] › ℹ info [forward_host] Migrating Up... migration file "20181019052346_forward_host.js" failed migration failed with error: show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only [7/12/2020] [3:34:15 PM] [Global ] › ✖ error show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only [7/12/2020] [3:34:16 PM] [Migrate ] › ℹ info Current database version: 20180929054513 [7/12/2020] [3:34:16 PM] [Migrate ] › ℹ info [forward_host] Migrating Up... migration file "20181019052346_forward_host.js" failed migration failed with error: show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only [7/12/2020] [3:34:16 PM] [Global ] › ✖ error show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only [7/12/2020] [3:34:17 PM] [Migrate ] › ℹ info Current database version: 20180929054513 [7/12/2020] [3:34:17 PM] [Migrate ] › ℹ info [forward_host] Migrating Up... migration file "20181019052346_forward_host.js" failed migration failed with error: show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only
kerem 2026-02-26 06:32:49 +03:00
kerem commented 2026-02-26 06:32:49 +03:00
Author
Owner
Copy link

@jaaacck commented on GitHub (Aug 27, 2020):

I am also getting the same issue with a brand new build today:

app_1  | [8/27/2020] [1:58:46 PM] [Migrate  ] › ℹ  info      Current database version: 20180929054513
app_1  | [8/27/2020] [1:58:46 PM] [Migrate  ] › ℹ  info      [forward_host] Migrating Up...
app_1  | migration file "20181019052346_forward_host.js" failed
app_1  | migration failed with error: show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only
app_1  | [8/27/2020] [1:58:46 PM] [Global   ] › ✖  error     show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only
app_1  | [8/27/2020] [1:58:47 PM] [Migrate  ] › ℹ  info      Current database version: 20180929054513
app_1  | [8/27/2020] [1:58:47 PM] [Migrate  ] › ℹ  info      [forward_host] Migrating Up...
app_1  | migration file "20181019052346_forward_host.js" failed
app_1  | migration failed with error: show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only
app_1  | [8/27/2020] [1:58:47 PM] [Global   ] › ✖  error     show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only
app_1  | [8/27/2020] [1:58:48 PM] [Migrate  ] › ℹ  info      Current database version: 20180929054513
app_1  | [8/27/2020] [1:58:48 PM] [Migrate  ] › ℹ  info      [forward_host] Migrating Up...
app_1  | migration file "20181019052346_forward_host.js" failed
app_1  | migration failed with error: show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only
app_1  | [8/27/2020] [1:58:48 PM] [Global   ] › ✖  error     show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only

Any suggestions?

<!-- gh-comment-id:681970476 --> @jaaacck commented on GitHub (Aug 27, 2020): I am also getting the same issue with a brand new build today: ``` app_1 | [8/27/2020] [1:58:46 PM] [Migrate ] › ℹ info Current database version: 20180929054513 app_1 | [8/27/2020] [1:58:46 PM] [Migrate ] › ℹ info [forward_host] Migrating Up... app_1 | migration file "20181019052346_forward_host.js" failed app_1 | migration failed with error: show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only app_1 | [8/27/2020] [1:58:46 PM] [Global ] › ✖ error show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only app_1 | [8/27/2020] [1:58:47 PM] [Migrate ] › ℹ info Current database version: 20180929054513 app_1 | [8/27/2020] [1:58:47 PM] [Migrate ] › ℹ info [forward_host] Migrating Up... app_1 | migration file "20181019052346_forward_host.js" failed app_1 | migration failed with error: show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only app_1 | [8/27/2020] [1:58:47 PM] [Global ] › ✖ error show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only app_1 | [8/27/2020] [1:58:48 PM] [Migrate ] › ℹ info Current database version: 20180929054513 app_1 | [8/27/2020] [1:58:48 PM] [Migrate ] › ℹ info [forward_host] Migrating Up... app_1 | migration file "20181019052346_forward_host.js" failed app_1 | migration failed with error: show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only app_1 | [8/27/2020] [1:58:48 PM] [Global ] › ✖ error show fields from `proxy_host` where field = 'forward_ip' - ER_OPEN_AS_READONLY: Table '/var/tmp/#sql_1_0.MAI' is read only ``` Any suggestions?
kerem commented 2026-02-26 06:32:49 +03:00
Author
Owner
Copy link

@jc21 commented on GitHub (Aug 27, 2020):

This is a mysql database issue. The MySQL database files have somehow changed permissions so that MySQL daemon is unable to open the file. Check the data permissions, if using a mysql/mariadb docker image for the database, the files need to be a specific user as well.

<!-- gh-comment-id:682214544 --> @jc21 commented on GitHub (Aug 27, 2020): This is a mysql database issue. The MySQL database files have somehow changed permissions so that MySQL daemon is unable to open the file. Check the data permissions, if using a mysql/mariadb docker image for the database, the files need to be a specific user as well.
kerem commented 2026-02-26 06:32:49 +03:00
Author
Owner
Copy link

@jaaacck commented on GitHub (Aug 28, 2020):

This is a mysql database issue. The MySQL database files have somehow changed permissions so that MySQL daemon is unable to open the file. Check the data permissions, if using a mysql/mariadb docker image for the database, the files need to be a specific user as well.

Permissions were fine. Owned by MySQL:

[root@rcn-ops-hg1-dev nginxproxymanager]# docker exec -it nginxproxymanager_db_1 ls -la /var/lib/mysql
total 122924
drwxr-xr-x    5 mysql    mysql          243 Aug 27 14:11 .
drwxr-xr-x    1 root     root            19 Mar 10 08:20 ..
-rw-rw----    1 mysql    mysql            2 Aug 27 14:11 718a022dde16.pid
-rw-rw----    1 mysql    mysql        24576 Aug 27 14:11 aria_log.00000001
-rw-rw----    1 mysql    mysql           52 Aug 27 14:11 aria_log_control
-rw-r-----    1 mysql    mysql         1940 Aug 27 14:11 ib_buffer_pool
-rw-rw----    1 mysql    mysql     50331648 Aug 27 14:11 ib_logfile0
-rw-rw----    1 mysql    mysql     50331648 Aug 27 13:54 ib_logfile1
-rw-rw----    1 mysql    mysql     12582912 Aug 27 14:11 ibdata1
-rw-rw----    1 mysql    mysql     12582912 Aug 27 14:11 ibtmp1
-rw-rw----    1 mysql    mysql            0 Aug 27 13:54 multi-master.info
drwx------    2 mysql    mysql         4096 Aug 27 13:54 mysql
drwx------    2 mysql    mysql         4096 Aug 27 13:54 npm
drwx------    2 mysql    mysql           20 Aug 27 13:54 performance_schema

Ended up moving to MySQL and container started and connected without any issues. I could replicate this on multiple nodes within our environment.

Here was my docker-compose.yml:

[root@rcn-ops-hg1-dev nginxproxymanager]# cat docker-compose.yml 
version: '2'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: always
    ports:
      - '6080:80'
      - '6081:81'
      - '6443:443'
    volumes:
      - /opt/proxymanager/config.json:/app/config/production.json
      - /opt/proxymanager/data:/data
      - /opy/proxymanager/letsencrypt:/etc/letsencrypt
    depends_on:
      - db
    environment:
      DISABLE_IPV6: 'true'

  db:
    image: 'jc21/mariadb-aria:10.4'
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: 'npm'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'npm'
      MYSQL_PASSWORD: 'npm'
    volumes:
      - /opt/proxymanager/data/mysql:/var/lib/mysql

Apart form the MariaDB hiccup the tool is working perfectly without a hitch

<!-- gh-comment-id:682440586 --> @jaaacck commented on GitHub (Aug 28, 2020): > This is a mysql database issue. The MySQL database files have somehow changed permissions so that MySQL daemon is unable to open the file. Check the data permissions, if using a mysql/mariadb docker image for the database, the files need to be a specific user as well. Permissions were fine. Owned by MySQL: ``` [root@rcn-ops-hg1-dev nginxproxymanager]# docker exec -it nginxproxymanager_db_1 ls -la /var/lib/mysql total 122924 drwxr-xr-x 5 mysql mysql 243 Aug 27 14:11 . drwxr-xr-x 1 root root 19 Mar 10 08:20 .. -rw-rw---- 1 mysql mysql 2 Aug 27 14:11 718a022dde16.pid -rw-rw---- 1 mysql mysql 24576 Aug 27 14:11 aria_log.00000001 -rw-rw---- 1 mysql mysql 52 Aug 27 14:11 aria_log_control -rw-r----- 1 mysql mysql 1940 Aug 27 14:11 ib_buffer_pool -rw-rw---- 1 mysql mysql 50331648 Aug 27 14:11 ib_logfile0 -rw-rw---- 1 mysql mysql 50331648 Aug 27 13:54 ib_logfile1 -rw-rw---- 1 mysql mysql 12582912 Aug 27 14:11 ibdata1 -rw-rw---- 1 mysql mysql 12582912 Aug 27 14:11 ibtmp1 -rw-rw---- 1 mysql mysql 0 Aug 27 13:54 multi-master.info drwx------ 2 mysql mysql 4096 Aug 27 13:54 mysql drwx------ 2 mysql mysql 4096 Aug 27 13:54 npm drwx------ 2 mysql mysql 20 Aug 27 13:54 performance_schema ``` Ended up moving to MySQL and container started and connected without any issues. I could replicate this on multiple nodes within our environment. Here was my docker-compose.yml: ```yaml [root@rcn-ops-hg1-dev nginxproxymanager]# cat docker-compose.yml version: '2' services: app: image: 'jc21/nginx-proxy-manager:latest' restart: always ports: - '6080:80' - '6081:81' - '6443:443' volumes: - /opt/proxymanager/config.json:/app/config/production.json - /opt/proxymanager/data:/data - /opy/proxymanager/letsencrypt:/etc/letsencrypt depends_on: - db environment: DISABLE_IPV6: 'true' db: image: 'jc21/mariadb-aria:10.4' restart: always environment: MYSQL_ROOT_PASSWORD: 'npm' MYSQL_DATABASE: 'npm' MYSQL_USER: 'npm' MYSQL_PASSWORD: 'npm' volumes: - /opt/proxymanager/data/mysql:/var/lib/mysql ``` Apart form the MariaDB hiccup the tool is working perfectly without a hitch
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#429
No description provided.