Skip to content

Internal 500 Error on the stream list page #4302

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
afexer opened this issue Jan 16, 2025 · 4 comments · Fixed by ZeroDeng01/nginx-proxy-manager#1 · May be fixed by #4381
Open

Internal 500 Error on the stream list page #4302

afexer opened this issue Jan 16, 2025 · 4 comments · Fixed by ZeroDeng01/nginx-proxy-manager#1 · May be fixed by #4381
Labels
bug

Comments

@afexer
Copy link

afexer commented Jan 16, 2025

Describe the bug
When going to the streams page in the latest version v2.12.2 I get a 500 Internal error message.
This is a line from the logs:
⚠ warning 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

Nginx Proxy Manager Version
2.12.2

To Reproduce
Steps to reproduce the behavior:

  1. Go to the streams page
  2. See the error

Expected behavior
List the streams

Screenshots

Screenshot 2025-01-15 at 9 06 10 PM
Screenshot 2025-01-15 at 9 09 25 PM

Operating System
Ubuntu 24 - using docker image
@afexer afexer added the bug label Jan 16, 2025
@truebigsand
Copy link

truebigsand commented Jan 20, 2025 •
edited
Loading

It's from here: (seems to be add for PostgreSQL)

nginx-proxy-manager/backend/internal/stream.js

Line 302 in 9687e9e

.orderByRaw('CAST(incoming_port AS INTEGER) ASC');

However, it goes wrong on MySQL 8.0, probably can be fixed by this:

--- CAST(`stream`.incoming_port AS INTEGER) DESC;
+++ CAST(`stream`.incoming_port AS UNSIGNED INTEGER) DESC;

or just replace INTEGER with UNSIGNED
PgSQL and MySQL conflict here, I'm not familiar with PgSQL so I cannot give a perfect solution, maybe just delete the sorting :)

@ZeroDeng01
Copy link

I have the same problem here, the current version 2.12.3, hope to fix

This was referenced Feb 21, 2025
Merged
Open
@mcrook587
Copy link

While your at it, maybe fix all the other shit thats plaguing this horrible project. Like maybe the custom locations that just about every other proxy manager on the planet earth has with ease but this project struggles.

This project is trash and dead!!!!

@vrichv
Copy link

vrichv commented Apr 27, 2025

same problem,hope to fix asap

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
5 participants
@vrichv @afexer @ZeroDeng01 @truebigsand @mcrook587