starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #4290] [BUG] Streams on Docker are broken completely since 2.12.X #2763

New issue

Open

opened 2026-02-26 07:36:42 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 07:36:42 +03:00

Owner

Originally created by @vextv on GitHub (Jan 11, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4290

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:

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

Originally created by @vextv on GitHub (Jan 11, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4290 **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](https://github.com/user-attachments/assets/b3ad98fb-cfc5-4c79-a87d-4f826930ad48) **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

kerem added the

stale

bug

labels

2026-02-26 07:36:42 +03:00

kerem commented

2026-02-26 07:36:43 +03:00

Author

Owner

@DJaq02 commented on GitHub (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.

@DJaq02 commented on GitHub (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.

kerem commented

2026-02-26 07:36:43 +03:00

Author

Owner

@jaitaiwan commented on GitHub (Jan 15, 2025):

I have an issue very similar to what's described here by @DJaq02 , if you recreate a container behind one of these, you're forced ot restart the stream to have it work again.

@jaitaiwan commented on GitHub (Jan 15, 2025): I have an issue very similar to what's described here by @DJaq02 , if you recreate a container behind one of these, you're forced ot restart the stream to have it work again.

kerem commented

2026-02-26 07:36:43 +03:00

Author

Owner

@jjcszxh commented on GitHub (Feb 5, 2025):

I have the same question

@jjcszxh commented on GitHub (Feb 5, 2025): I have the same question

kerem commented

2026-02-26 07:36:43 +03:00

Author

Owner

@G1ume commented on GitHub (Jul 30, 2025):

I'm experiencing the same issue. When checking the NPM logs, I see the following:

unknown format "ipv4" ignored in schema at path "#/properties/forwarding_host/anyOf/1"
unknown format "ipv4" ignored in schema at path "#/properties/forwarding_host/anyOf/1"
unknown format "ipv6" ignored in schema at path "#/properties/forwarding_host/anyOf/2"
unknown format "ipv6" ignored in schema at path "#/properties/forwarding_host/anyOf/2"

After pulling the latest image (dated JUL 30, 2025) and setting my own mysql db, NPM can save the stream without errors, BUT the stream is NOT effective.

UPDATE
solution:

add database configuration in docker-compose.yml

    environment:
      DB_MYSQL_HOST: ${IP_OR_DOMAIN}
      DB_MYSQL_PORT: ${PORT}
      DB_MYSQL_USER:  ${DB_USER}
      DB_MYSQL_PASSWORD: ${DB_PWD}
      DB_MYSQL_NAME: ${DB_NAME}

this would fix the ERROR "data must NOT have additional properties." and unknown format "ipv4" ignored in schema at path "#/properties/forwarding_host/anyOf/1".

Using network mode HOST instead or adding port like ${STREAM_PORT}:${STREAM_PORT} in docker-compose.yml, makes steams effective.

@G1ume commented on GitHub (Jul 30, 2025): I'm experiencing the same issue. When checking the NPM logs, I see the following: ``` unknown format "ipv4" ignored in schema at path "#/properties/forwarding_host/anyOf/1" unknown format "ipv4" ignored in schema at path "#/properties/forwarding_host/anyOf/1" unknown format "ipv6" ignored in schema at path "#/properties/forwarding_host/anyOf/2" unknown format "ipv6" ignored in schema at path "#/properties/forwarding_host/anyOf/2" ``` After pulling the latest image (dated JUL 30, 2025) and setting my own mysql db, NPM can save the stream without errors, BUT the stream is NOT effective. **UPDATE** solution: 1. add database configuration in docker-compose.yml ```yaml environment: DB_MYSQL_HOST: ${IP_OR_DOMAIN} DB_MYSQL_PORT: ${PORT} DB_MYSQL_USER: ${DB_USER} DB_MYSQL_PASSWORD: ${DB_PWD} DB_MYSQL_NAME: ${DB_NAME} ``` this would fix the ERROR "data must NOT have additional properties." and unknown format "ipv4" ignored in schema at path "#/properties/forwarding_host/anyOf/1". 2. Using network mode HOST instead or adding port like ${STREAM_PORT}:${STREAM_PORT} in docker-compose.yml, makes steams effective.

kerem commented

2026-02-26 07:36:43 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 6, 2026):

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

@github-actions[bot] commented on GitHub (Feb 6, 2026): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:36:43 +03:00

Author

Owner

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

I'm facing the same issue. Stream is not effective / applied even though it shows active on NPM dashboard.

@hrhv commented on GitHub (Feb 6, 2026): I'm facing the same issue. Stream is not effective / applied even though it shows active on NPM dashboard.

No milestone

No project

No assignees

1 participant

Notifications

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

No description provided.

Rows
Columns