starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #11] Unable to login #10

New issue

Closed

opened 2026-02-26 05:32:59 +03:00 by kerem · 7 comments

kerem commented

2026-02-26 05:32:59 +03:00

Owner

Originally created by @razzam21 on GitHub (Sep 3, 2018).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/11

NOTE: This is a first time trying to log in after deploying the container.

"Internal error" appears on the screen after entering the provided username and password.

This line appears in the logs.
[9/3/2018] [12:18:47 PM] [Express ] › ⚠ warning Configuration property "jwt.pub" is not defined

Originally created by @razzam21 on GitHub (Sep 3, 2018). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/11 NOTE: This is a first time trying to log in after deploying the container. "Internal error" appears on the screen after entering the provided username and password. This line appears in the logs. [9/3/2018] [12:18:47 PM] [Express ] › ⚠ warning Configuration property "jwt.pub" is not defined

kerem referenced this issue

2026-02-26 05:32:59 +03:00

[GH-ISSUE #10] Unable to install #11

kerem closed this issue

2026-02-26 05:32:59 +03:00

kerem commented

2026-02-26 05:32:59 +03:00

Author

Owner

@jc21 commented on GitHub (Sep 3, 2018):

A few questions...

Do you definitely have a config json file mounted as /app/config/production.json ?
Are you importing from a version 1 configuration?

@jc21 commented on GitHub (Sep 3, 2018): A few questions... 1. Do you definitely have a config json file mounted as `/app/config/production.json` ? 2. Are you importing from a version 1 configuration?

kerem commented

2026-02-26 05:33:00 +03:00

Author

Owner

@razzam21 commented on GitHub (Sep 3, 2018):

I see in the logs that the system modified the config.json that I pointed at /app/config/production.json. I am guessing it is doing that part like it is supposed to. It added a jwt section with keys and then acts like it can't find them.

It now looks like this:

{
"database": {
"engine": "mysql",
"host": "10.10.10.200",
"name": "nginx",
"user": "nginx",
"password": "nginx",
"port": 3306
},
"jwt": {
"key": "-----BEGIN RSA PRIVATE KEY-----[lots of characters]-----END RSA PRIVATE KEY-----",
"pub": "-----BEGIN PUBLIC KEY-----[lots of characters]----END PUBLIC KEY-----"
}
}

No I am not importing. This is a clean build/install.

@razzam21 commented on GitHub (Sep 3, 2018): 1) I see in the logs that the system modified the config.json that I pointed at /app/config/production.json. I am guessing it is doing that part like it is supposed to. It added a jwt section with keys and then acts like it can't find them. It now looks like this: { "database": { "engine": "mysql", "host": "10.10.10.200", "name": "nginx", "user": "nginx", "password": "nginx", "port": 3306 }, "jwt": { "key": "-----BEGIN RSA PRIVATE KEY-----[lots of characters]-----END RSA PRIVATE KEY-----", "pub": "-----BEGIN PUBLIC KEY-----[lots of characters]----END PUBLIC KEY-----" } } 2) No I am not importing. This is a clean build/install.

kerem commented

2026-02-26 05:33:00 +03:00

Author

Owner

@jc21 commented on GitHub (Sep 4, 2018):

That is very strange. I've just tested a clean install with the latest image and things are working fine. The fact that it wrote the keys to the file means it should be able to read from them. If you're using docker-compose, can you attach the output of this command: docker-compose config

Here's mine:

services:
  app:
    depends_on:
    - db
    environment:
      FORCE_COLOR: '1'
    image: jc21/nginx-proxy-manager:2
    ports:
    - 80:80/tcp
    - 81:81/tcp
    - 443:443/tcp
    restart: always
    volumes:
    - /opt/nginx-proxy-manager/config.json:/app/config/production.json:rw
    - /opt/nginx-proxy-manager/data:/data:rw
    - /opt/nginx-proxy-manager/letsencrypt:/etc/letsencrypt:rw
  db:
    environment:
      MYSQL_DATABASE: npm
      MYSQL_PASSWORD: npm
      MYSQL_ROOT_PASSWORD: npm
      MYSQL_USER: npm
    image: mariadb:10.3.7
    restart: always
    volumes:
    - /opt/nginx-proxy-manager/data/mysql:/var/lib/mysql:rw
version: '2.0'

Perhaps

@jc21 commented on GitHub (Sep 4, 2018): That is very strange. I've just tested a clean install with the latest image and things are working fine. The fact that it wrote the keys to the file means it should be able to read from them. If you're using docker-compose, can you attach the output of this command: `docker-compose config` Here's mine: ```yml services: app: depends_on: - db environment: FORCE_COLOR: '1' image: jc21/nginx-proxy-manager:2 ports: - 80:80/tcp - 81:81/tcp - 443:443/tcp restart: always volumes: - /opt/nginx-proxy-manager/config.json:/app/config/production.json:rw - /opt/nginx-proxy-manager/data:/data:rw - /opt/nginx-proxy-manager/letsencrypt:/etc/letsencrypt:rw db: environment: MYSQL_DATABASE: npm MYSQL_PASSWORD: npm MYSQL_ROOT_PASSWORD: npm MYSQL_USER: npm image: mariadb:10.3.7 restart: always volumes: - /opt/nginx-proxy-manager/data/mysql:/var/lib/mysql:rw version: '2.0' ``` Perhaps

kerem commented

2026-02-26 05:33:00 +03:00

Author

Owner

@SGStino commented on GitHub (Sep 7, 2018):

seeing the same issue, no docker compose was used.
However, recreating the container did solve the issue.

@SGStino commented on GitHub (Sep 7, 2018): seeing the same issue, no docker compose was used. However, recreating the container did solve the issue.

kerem commented

2026-02-26 05:33:00 +03:00

Author

Owner

@razzam21 commented on GitHub (Sep 7, 2018):

Sorry about the delay. I am not using docker-compose.

@razzam21 commented on GitHub (Sep 7, 2018): Sorry about the delay. I am not using docker-compose.

kerem commented

2026-02-26 05:33:00 +03:00

Author

Owner

@Aerya commented on GitHub (Sep 11, 2018):