Skip to content
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.

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

[BUG] Streams on Docker are broken completely since 2.12.X #4290

Open
vextv opened this issue Jan 11, 2025 · 1 comment
Open

[BUG] Streams on Docker are broken completely since 2.12.X #4290

vextv opened this issue Jan 11, 2025 · 1 comment
Labels

Comments

@vextv
Copy link

vextv commented Jan 11, 2025

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 / No

Describe the bug
Since any Version newer than 2.11.3 there seems to be a problem with saving the values you input to configure a stream. Any time you try to edit an already existing host and want to save your configuration (doesn't matter if you actually change any values or not) you get the error seen in the screenshot below.

Nginx Proxy Manager Version
2.12.X

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Streams'
  2. Click on 'Edit Stream' (you must already have one configured)
  3. Enter '443' as incoming port
  4. Enter an IP to Forward to (ex: 192.168.178.111)
  5. Enter '8443' as 'Forward Port'
  6. Click 'Save'
  7. See error:
    Screenshot 2025-01-11 130627

Expected behavior
In any version below 2.12.X you can enter this configuration and save it succesfully

Operating System
Standard Docker Container on Debian 12

Additional context
Tested in multiple Versions, the bug exists since "2.12.0" upwards

@vextv vextv added the bug label Jan 11, 2025
@DJaq02
Copy link

DJaq02 commented Jan 14, 2025

I have same problem. It occurs when Nginx Proxy Manager can't find the forward host. When the host is online you can delete the old Stream and create new and it will work. I also have found that Nginx Proxy Manager will crash if the forward host goes down. I have many times needed to delete Stream config files manually to get NPM to start again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants