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 #387] Migrations fail on initial start up #329

New issue
Closed
opened 2026-02-26 06:32:20 +03:00 by kerem · 1 comment
kerem commented 2026-02-26 06:32:20 +03:00
Owner
Copy link

Originally created by @chriskacerguis on GitHub (Apr 25, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/387

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Are you sure you're not using someone else's docker image?
  • If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?

Describe the bug
Starting the container for the first time, I am getting the following errors in my logs:

[4/25/2020] [8:24:25 PM] [Global   ] › ✖  error     insert into "setting" ("description", "id", "meta", "name", "value") values ($1, $2, $3, $4, $5) returning "id" - relation "setting" does not exist
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      Current database version: none
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] Migrating Up...
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] auth Table created
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] user Table created
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] user_permission Table created
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] proxy_host Table created
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] redirection_host Table created
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] dead_host Table created
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] stream Table created
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] access_list Table created
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] certificate Table created
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] access_list_auth Table created
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [initial-schema] audit_log Table created
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [websockets] Migrating Up...
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [websockets] proxy_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [forward_host] Migrating Up...
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [forward_host] proxy_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [http2_support] Migrating Up...
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [http2_support] proxy_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [http2_support] redirection_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [http2_support] dead_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [forward_scheme] Migrating Up...
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [forward_scheme] proxy_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [disabled] Migrating Up...
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [disabled] proxy_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [disabled] redirection_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [disabled] dead_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [disabled] stream Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [custom_locations] Migrating Up...
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [custom_locations] proxy_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [hsts] Migrating Up...
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [hsts] proxy_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [hsts] redirection_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [hsts] dead_host Table altered
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [settings] Migrating Up...
[4/25/2020] [8:24:26 PM] [Migrate  ] › ℹ  info      [settings] setting Table created
migration file "20190227065017_settings.js" failed
migration failed with error: insert into "setting" ("description", "id", "meta", "name", "value") values ($1, $2, $3, $4, $5) returning "id" - relation "setting" does not exist

[the log repeats that over and over]

  • What version of Nginx Proxy Manager is reported on the login page?
    v2.2.3

To Reproduce
Steps to reproduce the behavior:

  1. Created config.json file
  2. Ran the following in bash on Ubuntu 18.04
docker run --name=proxymanager \
--restart=always \
--network=internal \
-p 80:80 \
-p 81:81 \
-p 443:443 \
-v /opt/ssl:/ssl \
-v /opt/proxymanager/config.json:/app/config/production.json \
-v /opt/proxymanager/data:/data \
-v /opt/proxymanager/le:/etc/letsencrypt \
-d jc21/nginx-proxy-manager:latest

At that point I am unable to login, and when looking at the logs, I get the above error. (on a related note, I got 2 unable to find module body-parser and pg. I docker exec'd into the container and manually installed them with npm i pg and npm i body-parser

Interesting to note, the logs indicate that several tables were created, however when I log into the DB server, there are only two created migrations and migrations_lock

Expected behavior
I expected the container to start correctly, doing whatever it needs to do on first run. Then logging into and doing all the things.

Screenshots
n/a

Operating System
Ubuntu 18.04

Additional context
Docker version 19.03.8

root@server:/opt/proxymanager# more config.json 
{
  "database": {
    "engine": "postgres",
    "host": "XXXXXX",
    "name": "proxymanager",
    "user": "XXXXXX",
    "password": "XXXXXX",
    "port": 5432
  }
}
Originally created by @chriskacerguis on GitHub (Apr 25, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/387 **Checklist** - [x] Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - [x] Are you sure you're not using someone else's docker image? - [x] If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? **Describe the bug** Starting the container for the first time, I am getting the following errors in my logs: ```sh [4/25/2020] [8:24:25 PM] [Global ] › ✖ error insert into "setting" ("description", "id", "meta", "name", "value") values ($1, $2, $3, $4, $5) returning "id" - relation "setting" does not exist [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info Current database version: none [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] Migrating Up... [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] auth Table created [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] user Table created [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] user_permission Table created [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] proxy_host Table created [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] redirection_host Table created [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] dead_host Table created [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] stream Table created [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] access_list Table created [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] certificate Table created [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] access_list_auth Table created [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [initial-schema] audit_log Table created [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [websockets] Migrating Up... [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [websockets] proxy_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [forward_host] Migrating Up... [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [forward_host] proxy_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [http2_support] Migrating Up... [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [http2_support] proxy_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [http2_support] redirection_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [http2_support] dead_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [forward_scheme] Migrating Up... [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [forward_scheme] proxy_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [disabled] Migrating Up... [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [disabled] proxy_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [disabled] redirection_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [disabled] dead_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [disabled] stream Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [custom_locations] Migrating Up... [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [custom_locations] proxy_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [hsts] Migrating Up... [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [hsts] proxy_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [hsts] redirection_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [hsts] dead_host Table altered [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [settings] Migrating Up... [4/25/2020] [8:24:26 PM] [Migrate ] › ℹ info [settings] setting Table created migration file "20190227065017_settings.js" failed migration failed with error: insert into "setting" ("description", "id", "meta", "name", "value") values ($1, $2, $3, $4, $5) returning "id" - relation "setting" does not exist ``` [the log repeats that over and over] - What version of Nginx Proxy Manager is reported on the login page? v2.2.3 **To Reproduce** Steps to reproduce the behavior: 1. Created ```config.json``` file 2. Ran the following in bash on Ubuntu 18.04 ```sh docker run --name=proxymanager \ --restart=always \ --network=internal \ -p 80:80 \ -p 81:81 \ -p 443:443 \ -v /opt/ssl:/ssl \ -v /opt/proxymanager/config.json:/app/config/production.json \ -v /opt/proxymanager/data:/data \ -v /opt/proxymanager/le:/etc/letsencrypt \ -d jc21/nginx-proxy-manager:latest ``` At that point I am unable to login, and when looking at the logs, I get the above error. (on a related note, I got 2 unable to find module ```body-parser``` and ```pg```. I ```docker exec```'d into the container and manually installed them with ```npm i pg``` and ```npm i body-parser``` Interesting to note, the logs indicate that several tables were created, however when I log into the DB server, there are only two created ```migrations``` and ```migrations_lock``` **Expected behavior** I expected the container to start correctly, doing whatever it needs to do on first run. Then logging into and doing all the things. **Screenshots** n/a **Operating System** Ubuntu 18.04 **Additional context** Docker version 19.03.8 ```sh root@server:/opt/proxymanager# more config.json { "database": { "engine": "postgres", "host": "XXXXXX", "name": "proxymanager", "user": "XXXXXX", "password": "XXXXXX", "port": 5432 } } ```
kerem 2026-02-26 06:32:20 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-26 06:32:21 +03:00
Author
Owner
Copy link

@chriskacerguis commented on GitHub (Apr 25, 2020):

So I tried to use MySQL and it had no issues. I didn't see in the docs that Postgres would not work (but, I might have missed it), so feel free to close this if you don't want to support Postgres

[update]: ok, I found where you said you don't support it.

<!-- gh-comment-id:619438078 --> @chriskacerguis commented on GitHub (Apr 25, 2020): So I tried to use MySQL and it had no issues. I didn't see in the docs that Postgres would not work (but, I might have missed it), so feel free to close this if you don't want to support Postgres [update]: ok, I found where you said you don't support it.
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#329
No description provided.