NginxProxyManager / NginxProxyManager/nginx-proxy-manager

Error when accessing Stream UI ( error 500 )

Open
#4,556 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug stale
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

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
select stream.* from stream where is_deleted = 0 group by id order by CAST(incoming_port AS INTEGER) ASC - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'INTEGER) ASC' at line 1

I found this error when checking the NGINX Proxy Manager container log. Database is a MySQL native database on a separate server.

Nginx Proxy Manager Version
v2.12.3

To Reproduce
Steps to reproduce the behavior:

  1. Go to /nginx/stream
  2. See error

Expected behavior
Error 500

Screenshots

Image

Image

Operating System
Both database server and NPM is using Ubuntu 24.04

Additional context
MySQL version: 8.0.42
Docker version: 28.1.1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the /nginx/stream entry point and search for the reported SQL query, then reproduce the failure against MySQL 8.0.42 using the v2.12.3 Docker image. Done means the Stream UI loads without a 500 error and stream records can be accessed.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, mysql, nginx, typescript
Domain
backend, databases, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.