[GH-ISSUE #4448] Number of Hosts are not displayed in dashboard when mariadb backend is used #2847

New issue

Open

opened 2026-02-26 07:36:58 +03:00 by kerem · 7 comments

kerem commented 2026-02-26 07:36:58 +03:00

Owner

Copy link

Originally created by @targetingsnake on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4448

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
Numbers of Hosts are not displayed in Dashboard. See screenshot below. Instance is running with the mysql-backend. On another instance with the sqlite-database the issue is not there.

There is a HTTP-500-Error in API-Endpoint api/reports/hosts .

Nginx Proxy Manager Version
v2.12.3

To Reproduce
Steps to reproduce the behavior:

1. Login
2. Look at Dashboard

Expected behavior
Number of hosts in each category is displayed.

Screenshots

Operating System
VM with Debian and docker ($hostname is the hostname of the vm, removed for security reasons)
uname -a : Linux $hostname 6.1.0-31-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07) x86_64 GNU/Linux
Docker-version: Docker version 28.0.1, build 068a01e

Additional context
Docker-Compose content:

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
environment:
DB_MYSQL_HOST: "db"
DB_MYSQL_PORT: $dbport
DB_MYSQL_USER: "$username"
DB_MYSQL_PASSWORD: "$password"
DB_MYSQL_NAME: "$dbname"
# Uncomment this if IPv6 is not enabled on your host
# DISABLE_IPV6: 'true'
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
depends_on:
- db

db:
image: 'jc21/mariadb-aria:latest'
restart: unless-stopped
environment:
MYSQL_ROOT_PASSWORD: '$root_password'
MYSQL_DATABASE: '$dbname'
MYSQL_USER: '$username'
MYSQL_PASSWORD: '$password'
MARIADB_AUTO_UPGRADE: '1'
volumes:
- ./data/mysql:/var/lib/mysql

Originally created by @targetingsnake on GitHub (Mar 23, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4448 **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** Numbers of Hosts are not displayed in Dashboard. See screenshot below. Instance is running with the mysql-backend. On another instance with the sqlite-database the issue is not there. There is a HTTP-500-Error in API-Endpoint api/reports/hosts . **Nginx Proxy Manager Version** v2.12.3 **To Reproduce** Steps to reproduce the behavior: 1. Login 2. Look at Dashboard **Expected behavior** Number of hosts in each category is displayed. **Screenshots**  **Operating System** VM with Debian and docker ($hostname is the hostname of the vm, removed for security reasons) uname -a : Linux $hostname 6.1.0-31-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07) x86_64 GNU/Linux Docker-version: Docker version 28.0.1, build 068a01e **Additional context** Docker-Compose content: services: app: image: 'jc21/nginx-proxy-manager:latest' restart: unless-stopped ports: # These ports are in format <host-port>:<container-port> - '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 environment: DB_MYSQL_HOST: "db" DB_MYSQL_PORT: $dbport DB_MYSQL_USER: "$username" DB_MYSQL_PASSWORD: "$password" DB_MYSQL_NAME: "$dbname" # Uncomment this if IPv6 is not enabled on your host # DISABLE_IPV6: 'true' volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt depends_on: - db db: image: 'jc21/mariadb-aria:latest' restart: unless-stopped environment: MYSQL_ROOT_PASSWORD: '$root_password' MYSQL_DATABASE: '$dbname' MYSQL_USER: '$username' MYSQL_PASSWORD: '$password' MARIADB_AUTO_UPGRADE: '1' volumes: - ./data/mysql:/var/lib/mysql

kerem added the

stale

bug

labels 2026-02-26 07:36:58 +03:00

kerem commented 2026-02-26 07:36:58 +03:00

Author

Owner

Copy link

@targetingsnake commented on GitHub (Mar 23, 2025):

Logs saying this:

db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
db-1   | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
db-1   | 2025-03-23 10:41:25 12 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
db-1   | 2025-03-23 10:41:25 12 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
db-1   | 2025-03-23 10:41:25 13 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
db-1   | 2025-03-23 10:41:25 13 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).
app-1  | [3/23/2025] [10:41:25 AM] [Express  ] › ⚠  warning   select count(`id`) as `count` from `stream` where `is_deleted` = 0 and `owner_user_id` = 1 - Table 'npm.stream' doesn't exist

<!-- gh-comment-id:2746140098 --> @targetingsnake commented on GitHub (Mar 23, 2025): Logs saying this: ``` db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). db-1 | 2025-03-23 10:41:25 14 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). db-1 | 2025-03-23 10:41:25 12 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). db-1 | 2025-03-23 10:41:25 12 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). db-1 | 2025-03-23 10:41:25 13 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). db-1 | 2025-03-23 10:41:25 13 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). app-1 | [3/23/2025] [10:41:25 AM] [Express ] › ⚠ warning select count(`id`) as `count` from `stream` where `is_deleted` = 0 and `owner_user_id` = 1 - Table 'npm.stream' doesn't exist ```

kerem commented 2026-02-26 07:36:58 +03:00

Author

Owner

Copy link

@jc21 commented on GitHub (Mar 24, 2025):

Why wouldn't the stream table exist? There are 4 db migrations that create/alter it, so the app shouldn't have started when that table didn't exist.

<!-- gh-comment-id:2746850699 --> @jc21 commented on GitHub (Mar 24, 2025): Why wouldn't the `stream` table exist? There are 4 db migrations that create/alter it, so the app shouldn't have started when that table didn't exist.

kerem commented 2026-02-26 07:36:58 +03:00

Author

Owner

Copy link

@jc21 commented on GitHub (Mar 24, 2025):

I've added a test for this to the suite and it's passing.

<!-- gh-comment-id:2746904146 --> @jc21 commented on GitHub (Mar 24, 2025): I've added a [test for this to the suite](https://github.com/NginxProxyManager/nginx-proxy-manager/commit/5e66d677f1402b0414ae07124ad810fbc12c36ec) and it's passing.

kerem commented 2026-02-26 07:36:58 +03:00

Author

Owner

Copy link

@targetingsnake commented on GitHub (Mar 24, 2025):

i looked into it more detailed today. it turned out, that i also couldn't create the table as it was already there according to phpmyAdmin / the maria-db server. So i looked into the filesystem and found wrong file permissions on the files for those (see
Screenshot below ).

Way to solve:

1. move mariadb files from old location ./data/mysql to ./mysql with cp -aRv /data/mysql ./mysql after mkdir ./mysql
2. fix filepermissions on corrupted files with chmod -Rv 777 $tablename.* (replace $tablename with the required tablename)

@jc21 i think issue can be marked as resolved if that's fine with you

<!-- gh-comment-id:2748061892 --> @targetingsnake commented on GitHub (Mar 24, 2025): i looked into it more detailed today. it turned out, that i also couldn't create the table as it was already there according to phpmyAdmin / the maria-db server. So i looked into the filesystem and found wrong file permissions on the files for those (see Screenshot below ).  Way to solve: 1. move mariadb files from old location ./data/mysql to ./mysql with `cp -aRv /data/mysql ./mysql` after `mkdir ./mysql` 2. fix filepermissions on corrupted files with `chmod -Rv 777 $tablename.*` (replace $tablename with the required tablename) @jc21 i think issue can be marked as resolved if that's fine with you

kerem commented 2026-02-26 07:36:58 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Sep 23, 2025):

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

<!-- gh-comment-id:3322113189 --> @github-actions[bot] commented on GitHub (Sep 23, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented 2026-02-26 07:36:58 +03:00

Author

Owner

Copy link

@scharez commented on GitHub (Feb 6, 2026):

Hi @targetingsnake I am having the same problem on two npm instances. Are your steps to solve this issue still valid with the newer versions of npm?

2026-02-06  7:39:20 4 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').

2026-02-06  7:39:20 4 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).

<!-- gh-comment-id:3858573557 --> @scharez commented on GitHub (Feb 6, 2026): Hi @targetingsnake I am having the same problem on two npm instances. Are your steps to solve this issue still valid with the newer versions of npm? ``` 2026-02-06 7:39:20 4 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). 2026-02-06 7:39:20 4 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). ```

kerem commented 2026-02-26 07:36:58 +03:00

Author

Owner

Copy link

@targetingsnake commented on GitHub (Feb 6, 2026):

@scharez I can't tell you, i didn't ran in this issue again. Also i'm thinking about to migrate the schema with all the data onto my central mariadb host.

<!-- gh-comment-id:3861009158 --> @targetingsnake commented on GitHub (Feb 6, 2026): @scharez I can't tell you, i didn't ran in this issue again. Also i'm thinking about to migrate the schema with all the data onto my central mariadb host.

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

Subscribe

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#2847

No description provided.