[GH-ISSUE #1449] Host Streams IPv6 not possible #1120

Closed
opened 2026-02-26 06:35:51 +03:00 by kerem · 2 comments
Owner

Originally created by @Sirmike2 on GitHub (Oct 2, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1449

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

After creating a stream with Forward Host IPv6, the stream ist always offline.

Nginx Proxy Manager Version

v2.9.9

To Reproduce
Steps to reproduce the behavior:

  1. Go to Hosts --> Streams
  2. Click on Add Stream
  3. Insert Incoming Port, Forward Host IPv6, Forward Port and save
  4. Status is always Offline

Expected behavior

Stream should be online.

Screenshots

Operating System

Debian 10

Additional context

The IPv6 Host is reachable (Ping) over the IP. When I create a Proxyhost with this IPv6 IP the state is online but I get a 500 Internal Server Error. I have seen in the log, that there are no brackets infront and at the end of the IP. So the Port is directly behind the IP. Example: invalid port in upstream "fd00::aaaa:bbbb:cccc:dddd:80"
So I think this could be also the problem with the stream.

Originally created by @Sirmike2 on GitHub (Oct 2, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1449 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **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** <!-- A clear and concise description of what the bug is. --> After creating a stream with Forward Host IPv6, the stream ist always offline. **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> v2.9.9 **To Reproduce** Steps to reproduce the behavior: 1. Go to Hosts --> Streams 2. Click on Add Stream 3. Insert Incoming Port, Forward Host IPv6, Forward Port and save 4. Status is always Offline **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> Stream should be online. **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> Debian 10 **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. --> The IPv6 Host is reachable (Ping) over the IP. When I create a Proxyhost with this IPv6 IP the state is online but I get a 500 Internal Server Error. I have seen in the log, that there are no brackets infront and at the end of the IP. So the Port is directly behind the IP. Example: invalid port in upstream "fd00::aaaa:bbbb:cccc:dddd:80" So I think this could be also the problem with the stream.
kerem 2026-02-26 06:35:51 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@github-actions[bot] commented on GitHub (Mar 3, 2024):

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

<!-- gh-comment-id:1974976671 --> @github-actions[bot] commented on GitHub (Mar 3, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Apr 16, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2808021481 --> @github-actions[bot] commented on GitHub (Apr 16, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
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#1120
No description provided.