AnID-Aux commented 1 year ago

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes
Are you sure you're not using someone else's docker image?
- Yes
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug Logging into the admin interface no longer works. Mistake: Internal Error and sporadically Bad Gateway. Standard Username and Password don't work as well. Misstake: No relevant user found. Going back to 2.9.22 is working.

Nginx Proxy Manager Version v2.10.0

To Reproduce Steps to reproduce the behavior:

Go to the Admin-Interface
Click on E-Mail-Adress and Password an Login
See error "Internal Error"

Bark33p3r commented 1 year ago

I get the same error at first. Few seconds later ist shows: "No relevant user found". Reverted to v2.9.22 and I can login again.

JamesMCL44 commented 1 year ago

Just to confirm the same error on my side at my fresh install and the temporary "fix" is to downgrade to v2.9.22

shepherds-git commented 1 year ago

I had the same problem, but I found out that I could login with the default credentials (admin@example.com...). Afterwards I saw an empty configuration in the dashboard, with 0 proxy hosts. But in the background the existing configuration was running in the nginx proxy. I could access my hosts from the web. Fir me it seems that the running configuration and the web-interface aren't synchronized. Maybe this helps to find the issue.

stanthewizzard commented 1 year ago

give right to the data and letsencrypt folder it's 911 now (without puid or guid) chown 0777 worked for me

Bark33p3r commented 1 year ago

Thanks for the advise When I change owner and group to 0777

and run "docker-compose up -d" it will change to 911 again and I'm getting the same error.

(name and password removed for the screenshot)

Nessiroj commented 1 year ago

give right to the data and letsencrypt folder it's 911 now (without puid or guid) chown 0777 worked for me

Thanks for this, this fixed my issues aswell after trying to troubleshoot it for 3 hours

I had the same problem, but I found out that I could login with the default credentials (admin@example.com...). Afterwards I saw an empty configuration in the dashboard, with 0 proxy hosts. But in the background the existing configuration was running in the nginx proxy. I could access my hosts from the web. Fir me it seems that the running configuration and the web-interface aren't synchronized. Maybe this helps to find the issue.

This is the next issue after the chown 0777 thankfully my hosts are working again, just can't access the npm to configure them

stanthewizzard commented 1 year ago

Thanks for the advise When I change owner and group to 0777

and run "docker-compose up -d" it will change to 911 again and I'm getting the same error.

(name and password removed for the screenshot)

In your case the databse is empty ... try to access it with phpmyadmin or if you are a warrior (I'm tired today) with command line

meistermopper commented 1 year ago

give right to the data and letsencrypt folder it's 911 now (without puid or guid) chown 0777 worked for me

Thanks for this, this fixed my issues aswell after trying to troubleshoot it for 3 hours

I had the same problem, but I found out that I could login with the default credentials (admin@example.com...). Afterwards I saw an empty configuration in the dashboard, with 0 proxy hosts. But in the background the existing configuration was running in the nginx proxy. I could access my hosts from the web. Fir me it seems that the running configuration and the web-interface aren't synchronized. Maybe this helps to find the issue.

This is the next issue after the chown 0777 thankfully my hosts are working again, just can't access the npm to configure them

However, I see a security problem there with 0777. Before the update the folders data and letsencrypt have the rights

drwxr-xr-x 755 root root data.

For me, in any case, the version 2.10.0 is not usable.

meistermopper commented 1 year ago

With version 2.10.1 access to the MariaDb 10.9.3 database is not possible. With version 2.9.21 it still works fine.

Here is the log from npm:

-------------------------------------
 _   _ ____  __  __
| \ | |  _ \|  \/  |
|  \| | |_) | |\/| |
| |\  |  __/| |  | |
|_| \_|_|   |_|  |_|
-------------------------------------
User UID: 911
User GID: 911
-------------------------------------
s6-rc: info: service prepare successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service frontend: starting
s6-rc: info: service backend: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service frontend successfully started
s6-rc: info: service backend successfully started
❯ Starting nginx ...
s6-rc: info: service legacy-services: starting
❯ Starting backend ...
s6-rc: info: service legacy-services successfully started
[3/29/2023] [2:22:39 PM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
[3/29/2023] [2:22:39 PM] [Global   ] › ℹ  info      Creating a new JWT key pair...
[3/29/2023] [2:22:54 PM] [Global   ] › ℹ  info      Wrote JWT key pair to config file: /data/keys.json
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      Current database version: none
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] auth Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] user Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] user_permission Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] proxy_host Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] redirection_host Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] dead_host Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] stream Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] access_list Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] certificate Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] access_list_auth Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [initial-schema] audit_log Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [websockets] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [websockets] proxy_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [forward_host] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [forward_host] proxy_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [http2_support] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [http2_support] proxy_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [http2_support] redirection_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [http2_support] dead_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [forward_scheme] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [forward_scheme] proxy_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [disabled] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [disabled] proxy_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [disabled] redirection_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [disabled] dead_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [disabled] stream Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [custom_locations] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [custom_locations] proxy_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [hsts] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [hsts] proxy_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [hsts] redirection_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [hsts] dead_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [settings] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [settings] setting Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [access_list_client] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [access_list_client] access_list_client Table created
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [access_list_client] access_list Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [access_list_client_fix] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [access_list_client_fix] access_list Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [pass_auth] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [pass_auth] access_list Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [redirection_scheme] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [redirection_scheme] redirection_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [redirection_status_code] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [redirection_status_code] redirection_host Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [stream_domain] stream Table altered
[3/29/2023] [2:22:55 PM] [Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
[3/29/2023] [2:22:55 PM] [Setup    ] › ℹ  info      Creating a new user: admin@example.com with password: changeme
[3/29/2023] [2:22:56 PM] [Setup    ] › ℹ  info      Initial admin setup completed
[3/29/2023] [2:22:56 PM] [Setup    ] › ℹ  info      Default settings added
[3/29/2023] [2:22:56 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[3/29/2023] [2:22:56 PM] [Setup    ] › ℹ  info      Logrotate completed.
[3/29/2023] [2:22:56 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[3/29/2023] [2:22:56 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[3/29/2023] [2:22:56 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[3/29/2023] [2:22:56 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[3/29/2023] [2:22:57 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[3/29/2023] [2:22:57 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[3/29/2023] [2:22:57 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[3/29/2023] [2:22:57 PM] [Global   ] › ℹ  info      Backend PID 168 listening on port 3000 ...
[3/29/2023] [2:22:59 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[3/29/2023] [2:23:00 PM] [SSL      ] › ℹ  info      Renew Complete

Log from MariaDb:

2023-03-24 14:25:49 15 [Warning] Aborted connection 15 to db: 'npm' user: 'npm' host: '172.18.0.13' (Got an error reading communication packets)
2023-03-24 14:25:49 8 [Warning] Aborted connection 8 to db: 'npm' user: 'npm' host: '172.18.0.13' (Got an error reading communication packets)
2023-03-27 14:09:09 0 [Note] mariadbd (initiated by: unknown): Normal shutdown
2023-03-27 14:09:09 0 [Note] InnoDB: FTS optimize thread exiting.
2023-03-27 14:09:09 0 [Note] InnoDB: Starting shutdown...
2023-03-27 14:09:09 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2023-03-27 14:09:09 0 [Note] InnoDB: Buffer pool(s) dump completed at 230327 14:09:09
2023-03-27 14:09:10 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2023-03-27 14:09:10 0 [Note] InnoDB: Shutdown completed; log sequence number 69843597; transaction id 708952
2023-03-27 14:09:10 0 [Note] mariadbd: Shutdown complete
2023-03-27 14:30:14+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.3+maria~ubu2204 started.
2023-03-27 14:30:16+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2023-03-27 14:30:16+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.3+maria~ubu2204 started.
2023-03-27 14:30:16+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2023-03-27 14:30:17 0 [Note] mariadbd (server 10.9.3-MariaDB-1:10.9.3+maria~ubu2204) starting as process 1 ...
2023-03-27 14:30:17 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-03-27 14:30:17 0 [Note] InnoDB: Number of transaction pools: 1
2023-03-27 14:30:17 0 [Note] InnoDB: Using generic crc32 instructions
2023-03-27 14:30:17 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2023-03-27 14:30:17 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2023-03-27 14:30:17 0 [Note] InnoDB: Completed initialization of buffer pool
2023-03-27 14:30:17 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2023-03-27 14:30:17 0 [Note] InnoDB: 128 rollback segments are active.
2023-03-27 14:30:17 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2023-03-27 14:30:17 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2023-03-27 14:30:17 0 [Note] InnoDB: log sequence number 69843597; transaction id 708953
2023-03-27 14:30:17 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-03-27 14:30:17 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2023-03-27 14:30:17 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2023-03-27 14:30:17 0 [Note] Server socket created on IP: '0.0.0.0'.
2023-03-27 14:30:17 0 [Note] Server socket created on IP: '::'.
2023-03-27 14:30:17 0 [Warning] 'proxies_priv' entry '@% root@92f24548261a' ignored in --skip-name-resolve mode.
2023-03-27 14:30:17 0 [Note] InnoDB: Buffer pool(s) load completed at 230327 14:30:17
2023-03-27 14:30:17 0 [Note] mariadbd: ready for connections.
Version: '10.9.3-MariaDB-1:10.9.3+maria~ubu2204'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
2023-03-27 15:13:06 0 [Note] mariadbd (initiated by: unknown): Normal shutdown
2023-03-27 15:13:06 0 [Note] InnoDB: FTS optimize thread exiting.
2023-03-27 15:13:06 0 [Note] InnoDB: Starting shutdown...
2023-03-27 15:13:06 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2023-03-27 15:13:06 0 [Note] InnoDB: Buffer pool(s) dump completed at 230327 15:13:06
2023-03-27 15:13:06 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2023-03-27 15:13:06 0 [Note] InnoDB: Shutdown completed; log sequence number 69849334; transaction id 709022
2023-03-27 15:13:06 0 [Note] mariadbd: Shutdown complete
2023-03-27 15:28:24+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.3+maria~ubu2204 started.
2023-03-27 15:28:25+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2023-03-27 15:28:25+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.3+maria~ubu2204 started.
2023-03-27 15:28:26+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2023-03-27 15:28:26 0 [Note] mariadbd (server 10.9.3-MariaDB-1:10.9.3+maria~ubu2204) starting as process 1 ...
2023-03-27 15:28:27 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-03-27 15:28:27 0 [Note] InnoDB: Number of transaction pools: 1
2023-03-27 15:28:27 0 [Note] InnoDB: Using generic crc32 instructions
2023-03-27 15:28:27 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2023-03-27 15:28:27 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2023-03-27 15:28:27 0 [Note] InnoDB: Completed initialization of buffer pool
2023-03-27 15:28:27 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2023-03-27 15:28:27 0 [Note] InnoDB: 128 rollback segments are active.
2023-03-27 15:28:27 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2023-03-27 15:28:27 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2023-03-27 15:28:27 0 [Note] InnoDB: log sequence number 69849334; transaction id 709014
2023-03-27 15:28:27 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2023-03-27 15:28:27 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-03-27 15:28:27 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2023-03-27 15:28:27 0 [Note] Server socket created on IP: '0.0.0.0'.
2023-03-27 15:28:27 0 [Note] Server socket created on IP: '::'.
2023-03-27 15:28:27 0 [Note] InnoDB: Buffer pool(s) load completed at 230327 15:28:27
2023-03-27 15:28:27 0 [Warning] 'proxies_priv' entry '@% root@92f24548261a' ignored in --skip-name-resolve mode.
2023-03-27 15:28:27 0 [Note] mariadbd: ready for connections.
Version: '10.9.3-MariaDB-1:10.9.3+maria~ubu2204'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
2023-03-29 13:59:30+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.3+maria~ubu2204 started.
2023-03-29 13:59:32+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2023-03-29 13:59:32+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.3+maria~ubu2204 started.
2023-03-29 13:59:34+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2023-03-29 13:59:34 0 [Note] mariadbd (server 10.9.3-MariaDB-1:10.9.3+maria~ubu2204) starting as process 1 ...
2023-03-29 13:59:34 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-03-29 13:59:34 0 [Note] InnoDB: Number of transaction pools: 1
2023-03-29 13:59:34 0 [Note] InnoDB: Using generic crc32 instructions
2023-03-29 13:59:34 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2023-03-29 13:59:34 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2023-03-29 13:59:35 0 [Note] InnoDB: Completed initialization of buffer pool
2023-03-29 13:59:35 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2023-03-29 13:59:35 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=69849318
2023-03-29 13:59:35 0 [Note] InnoDB: Starting final batch to recover 17 pages from redo log.
2023-03-29 13:59:35 0 [Note] InnoDB: 128 rollback segments are active.
2023-03-29 13:59:35 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2023-03-29 13:59:35 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2023-03-29 13:59:35 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2023-03-29 13:59:35 0 [Note] InnoDB: log sequence number 69882909; transaction id 709335
2023-03-29 13:59:35 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2023-03-29 13:59:35 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-03-29 13:59:35 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2023-03-29 13:59:35 0 [Note] InnoDB: Buffer pool(s) load completed at 230329 13:59:35
2023-03-29 13:59:35 0 [Note] Server socket created on IP: '0.0.0.0'.
2023-03-29 13:59:35 0 [Note] Server socket created on IP: '::'.
2023-03-29 13:59:35 0 [Warning] 'proxies_priv' entry '@% root@92f24548261a' ignored in --skip-name-resolve mode.
2023-03-29 13:59:35 0 [Note] mariadbd: ready for connections.
Version: '10.9.3-MariaDB-1:10.9.3+maria~ubu2204'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
2023-03-29 14:22:31 13 [Warning] Aborted connection 13 to db: 'npm' user: 'npm' host: '172.18.0.3' (Got an error reading communication packets)
2023-03-29 14:22:32 14 [Warning] Aborted connection 14 to db: 'npm' user: 'npm' host: '172.18.0.3' (Got an error reading communication packets)

Portainer stack:

version: "3"
services:

#  _   _       _              _____                       __  __                                   
# | \ | |     (_)            |  __ \                     |  \/  |                                  
# |  \| | __ _ _ _ __ __  __ | |__) | __ _____  ___   _  | \  / | __ _ _ __   __ _  __ _  ___ _ __ 
# | . ` |/ _` | | '_ \\ \/ / |  ___/ '__/ _ \ \/ / | | | | |\/| |/ _` | '_ \ / _` |/ _` |/ _ \ '__|
# | |\  | (_| | | | | |>  <  | |   | | | (_) >  <| |_| | | |  | | (_| | | | | (_| | (_| |  __/ |   
# |_| \_|\__, |_|_| |_/_/\_\ |_|   |_|  \___/_/\_\\__, | |_|  |_|\__,_|_| |_|\__,_|\__, |\___|_|   
#         __/ |                                    __/ |                            __/ |          
#        |___/                                    |___/                            |___/           

  reverseproxy:
    image: jc21/nginx-proxy-manager:2.10.1
    container_name: npm
    restart: always
    ports:
      - 80:80
      - 81:81
      - 443:443
    environment:
      # if you want pretty colors in your docker logs:
      - FORCE_COLOR=1
      # Uncomment this if IPv6 is not enabled on your host
      # DISABLE_IPV6: 'true'
    volumes:
      - ./npm/config.json:/app/config/production.json
      - ./npm/data:/data
      - ./npm/letsencrypt:/etc/letsencrypt
    logging:
        driver: "json-file"
        options:
            max-size: "5m"
            max-file: "5"
            compress: "true"
    depends_on:
      - reverseproxydb

 # __  __            _       _____  _     
 #|  \/  |          (_)     |  __ \| |    
 #| \  / | __ _ _ __ _  __ _| |  | | |__  
 #| |\/| |/ _` | '__| |/ _` | |  | | '_ \ 
 #| |  | | (_| | |  | | (_| | |__| | |_) |
 #|_|  |_|\__,_|_|  |_|\__,_|_____/|_.__/ 

  reverseproxydb:
    image: mariadb:latest
    container_name: npm-db
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: "npm"
      MYSQL_DATABASE: "npm"
      MYSQL_USER: "npm"
      MYSQL_PASSWORD: "npm"
      # nach Fehler eingefügt: [ERROR] Incorrect definition of table mysql.column_stats: expected column
      MARIADB_AUTO_UPGRADE: "1"
      MARIADB_INITDB_SKIP_TZINFO: "1"
    volumes:
      - ./npm/data/mysql:/var/lib/mysql

purpletoad2020 commented 1 year ago

Same issue here after upgraded to 2.10.1, no longer be able to login got Bad Gateway error

However, the actual proxy is still function, all proxied website still be able to access

AlexKusnezov commented 1 year ago

same here No relevant user found

Bark33p3r commented 1 year ago

same here No relevant user found

Just installed 2.10.2 . Still the same problem.

popallo commented 1 year ago

same here No relevant user found

Just installed 2.10.2 . Still the same problem.

if you use a mysql database and the configuration of this one is in the file "npm-config.json" then it is normal that it does not work, this file is not used any more and it is necessary to pass by the environment variables.

Bark33p3r commented 1 year ago

Great, Thanks a lot for the advise!!! Now it works.

nobrainer instruction for people like me: Update your docker Loginin with:

Email: admin@example.com
Password: changeme

fill out your name and mail in the pop-up change the password in the next upcoming pop-up (old pw, 2x new pw)

Thanks a lot @popallo

AlexKusnezov commented 1 year ago

@Bark33p3r did that and it worked, however the hosts are not showing up:

How to deal with that? They're still working though

popallo commented 1 year ago

@Bark33p3r did that and it worked, however the hosts are not showing up: How to deal with that? They're still working though

Your docker instance is probably using an sqlite database while I imagine you were on mysql before? If so, read my previous comment, it may help you.

AlexKusnezov commented 1 year ago

@popallo

if you use a mysql database and the configuration of this one is in the file "npm-config.json" then it is normal that it does not work, this file is not used any more and it is necessary to pass by the environment variables

Are you refring to this?

What do I have to do in my sepcific case, please take a look at my config:

version: '3'
services:

  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '85:80' #HTTP Traffic
      - '81:81' #Dashboard Port
      - '448:443' #HTTPS Traffic
    networks:
            staticnet:
                      ipv4_address: 172.18.0.3

    volumes:
      - /mnt/nginx-proxy-manager/config.json:/app/config/production.json
      - /mnt/nginx-proxy-manager/data:/data
      - /mnt/nginx-proxy-manager/letsencrypt:/etc/letsencrypt
  db:
    image: 'jc21/mariadb-aria:latest'
    restart: unless-stopped
    networks:
            staticnet:
                      ipv4_address: 172.18.0.2
    environment:
      MYSQL_ROOT_PASSWORD: 'npm'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'xxx'
      MYSQL_PASSWORD: 'xxx'
    volumes:
      - /mnt/nginx-proxy-manager/data/mysql:/var/lib/mysql

networks:
    staticnet:
        ipam:
            driver: default
            config:
                - subnet: 172.18.0.0/16

popallo commented 1 year ago

volumes:

/mnt/nginx-proxy-manager/config.json:/app/config/production.json

This configuration's file is not used anymore. You need to add "environment:" with some specifics variables under "app:" like in this example : https://nginxproxymanager.com/setup/#using-mysql-mariadb-database

AlexKusnezov commented 1 year ago

@popallo thanks, change my config to the following:

version: '3.8'
services:

  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '85:80' #HTTP Traffic
      - '81:81' #Dashboard Port
      - '448:443' #HTTPS Traffic

    environment:
      # Mysql/Maria connection parameters:
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: "xxx"
      DB_MYSQL_PASSWORD: "xxx"
      DB_MYSQL_NAME: "npm"
      # Uncomment this if IPv6 is not enabled on your host
      # DISABLE_IPV6: 'true'
    networks:
            staticnet:
                      ipv4_address: 172.18.0.3

    volumes:
      - /mnt/nginx-proxy-manager/config.json:/app/config/production.json
      - /mnt/nginx-proxy-manager/data:/data
      - /mnt/nginx-proxy-manager/letsencrypt:/etc/letsencrypt
    depends_on:
      - db

  db:
    image: 'jc21/mariadb-aria:latest'
    restart: unless-stopped
    networks:
            staticnet:
                      ipv4_address: 172.18.0.2
    environment:
      MYSQL_ROOT_PASSWORD: 'npm'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'xxx'
      MYSQL_PASSWORD: 'xxx'
    volumes:
      - /mnt/nginx-proxy-manager/mysql:/var/lib/mysql

networks:
    staticnet:
        ipam:
            driver: default
            config:
                - subnet: 172.18.0.0/16

still can't see my hosts, but they're still working, any idea how to display them?

AlexKusnezov commented 1 year ago

@popallo nevermid, I solved this now:

Since I had to change /mnt/nginx-proxy-manager/data/mysql:/var/lib/mysql to /mnt/nginx-proxy-manager/mysql:/var/lib/mysql (otherwise I would get Bad Gateway), I just copied manually the mysql fodler over and now it shows my host:

SSpt1978 commented 1 year ago

Hi, i have this docker compose and after update to 2.10.2 can't login. Anything wrong? Reverted to version 2.9.22

version: "3.8" services: app: image: 'jc21/nginx-proxy-manager:latest' restart: unless-stopped ports:

These ports are in format :

  - '80:80' # Public HTTP Port
  - '443:443' # Public HTTPS Port
  - '81:81' # Admin Web Port
  # Add any other Stream port you want to expose
  # - '21:21' # FTP
# - '22:22' # SFTP
environment:
  DB_MYSQL_HOST: "db"
  DB_MYSQL_PORT: 3306
  DB_MYSQL_USER: "XXXXXXXXXXXX"
  DB_MYSQL_PASSWORD: "XXXXXXXXXXXX"
  DB_MYSQL_NAME: "npm"
  # Uncomment this if IPv6 is not enabled on your host
  # DISABLE_IPV6: 'true'
volumes:
  - ./_hsts.conf:/app/templates/_hsts.conf:ro
  - ./data:/data
  - ./letsencrypt:/etc/letsencrypt
depends_on:
  - db

db: image: 'jc21/mariadb-aria:latest' restart: unless-stopped environment: MYSQL_ROOT_PASSWORD: 'XXXXXXXXXXXXXX' MYSQL_DATABASE: 'npm' MYSQL_USER: 'XXXXXXXXXXXXX' MYSQL_PASSWORD: 'XXXXXXXXXXXXXXXXX' volumes:

./data/mysql:/var/lib/mysql

AlexKusnezov commented 1 year ago

@SSpt1978 the mysql folder has to be outside of the data folder see my last comment

stanthewizzard commented 1 year ago

In my case it’s inside data Rebuild with docker-compose Restarted Works Reverse proxy and administration pages

SSpt1978 commented 1 year ago

AlexKusnezov

Thanks, it worked

poltrian commented 1 year ago

I use MaraDB Docker with Nginx Proxy Manager. When i use admin@example.com i got also No relevant user found

Great, Thanks a lot for the advise!!! Now it works.

nobrainer instruction for people like me: Update your docker Loginin with:
* Email: [admin@example.com](mailto:admin@example.com)

* Password: changeme
fill out your name and mail in the pop-up change the password in the next upcoming pop-up (old pw, 2x new pw)

Thanks a lot @popallo

kosymodo commented 1 year ago

I too am having issues - updated to v2.10.2, proxies are working, but can't administer them

I've followed all the above advice, but still have a blank list :(

@AlexKusnezov @Bark33p3r @popallo can any of you help me?

funky123 commented 1 year ago

i have same issue. can login with default creds but cant mange my hosts etc. Upgraded from Version v2.9.18 to v2.10.3

wodan66 commented 1 year ago

Since I had to change /mnt/nginx-proxy-manager/data/mysql:/var/lib/mysql to /mnt/nginx-proxy-manager/mysql:/var/lib/mysql (otherwise I would get Bad Gateway), I just copied manually the mysql fodler over and now it shows my host:

mv mysql out of data and adjust the docker compose file accordingly solved my issues as well. Thanks

github-actions[bot] commented 8 months ago

Issue is now considered stale. If you want to keep it open, please comment :+1:

Eremar87 commented 6 months ago

I have the same problem. After update, i can't manage my hosts (which works at moment...). I tried to move db outside data, chmod 777 but nothing works.

Can you help me? I'm not expert so pls be more clear. I tried to adjust my docker configuration, but I'm doing wrong.

I use portainer to manage everything on a raspy.

The db and nginx app seems working...

NginxProxyManager / nginx-proxy-manager

Logging into the admin interface no longer works. Mistake: Internal Error #2754

These ports are in format :