NginxProxyManager / NginxProxyManager/nginx-proxy-manager
[BUG] Streams on Docker are broken completely since 2.12.X
Nobody has claimed this yet.
- 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:latestdocker 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:
- Go to 'Streams'
- Click on 'Edit Stream' (you must already have one configured)
- Enter '443' as incoming port
- Enter an IP to Forward to (ex: 192.168.178.111)
- Enter '8443' as 'Forward Port'
- Click 'Save'
- See error:
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Streams entry point in the Docker image and reproduce editing an existing stream with incoming port 443, destination 192.168.178.111, and forward port 8443. Trace the edit/save path to identify why unchanged or updated values fail after version 2.11.3, then verify that the configuration saves successfully without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx, typescript
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100