When trying to use an IPv6 address as target through Newt, I get a "Bad Gateway" error.
Environment
OS Type & Version: NixOS 25.11 mixed with unstable overlays
Pangolin Version: 1.15.3
Gerbil Version: 1.3.0
Traefik Version: 3.6.10
Newt Version: 1.10.3 (in Docker on Synology with host networking)
Olm Version: none
To Reproduce
Create a public resource pointing to an HTTP service on an IPv6 address reachable by the Newt server.
Go to that resource
Receive a "Bad Gateway" error
Note that the website prevents me from entering an IPv6 address that is encapsulated with [] , so the unencapsulated form seems to be correct in this context.
Also notable:
The health checks by Newt are successful, so there is no connectivity issue between Newt and the target
An IPv4 target through the same Newt site is reachable without issue.
Unfortunately, even after enabling debug logging in Newt, and looking at the logs for pangolin, gerbil and traefik, I was unable to find any indication of where things are going wrong.
Expected Behavior
There is no "Bad Gateway" error, the HTTP service is available through Pangolin.
Workaround
Create an internal AAAA DNS entry for the target IP and point Pangolin to that. This indicates to me that the issue is caused by some component not parsing the target address correctly - I assume some component expects the aforementioned brackets around the IPv6 address and fails because they're missing.
Originally created by @jess-sch on GitHub (Mar 22, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2688
### Describe the Bug
When trying to use an IPv6 address as target through Newt, I get a "Bad Gateway" error.
### Environment
- OS Type & Version: NixOS 25.11 mixed with unstable overlays
- Pangolin Version: 1.15.3
- Gerbil Version: 1.3.0
- Traefik Version: 3.6.10
- Newt Version: 1.10.3 (in Docker on Synology with host networking)
- Olm Version: none
### To Reproduce
1. Create a public resource pointing to an HTTP service on an IPv6 address reachable by the Newt server.
2. Go to that resource
3. Receive a "Bad Gateway" error
<img width="1848" height="444" alt="Image" src="https://github.com/user-attachments/assets/a16032e5-efe0-4d2c-bdd5-b59473aa49a9" />
Note that the website prevents me from entering an IPv6 address that is encapsulated with `[]` , so the unencapsulated form seems to be correct in this context.
Also notable:
* The health checks by Newt are successful, so there is no connectivity issue between Newt and the target
* An IPv4 target through the same Newt site is reachable without issue.
Unfortunately, even after enabling debug logging in Newt, and looking at the logs for pangolin, gerbil and traefik, I was unable to find any indication of where things are going wrong.
### Expected Behavior
There is no "Bad Gateway" error, the HTTP service is available through Pangolin.
### Workaround
Create an internal AAAA DNS entry for the target IP and point Pangolin to that. This indicates to me that the issue is caused by some component not parsing the target address correctly - I assume some component expects the aforementioned brackets around the IPv6 address and fails because they're missing.
<!-- gh-comment-id:4106668161 -->
@LaurenceJJones commented on GitHub (Mar 22, 2026):
Surprised the healthcheck are working.
This will be fixed once https://github.com/fosrl/pangolin/pull/2667 is released.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jess-sch on GitHub (Mar 22, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2688
Describe the Bug
When trying to use an IPv6 address as target through Newt, I get a "Bad Gateway" error.
Environment
To Reproduce
Note that the website prevents me from entering an IPv6 address that is encapsulated with
[], so the unencapsulated form seems to be correct in this context.Also notable:
Unfortunately, even after enabling debug logging in Newt, and looking at the logs for pangolin, gerbil and traefik, I was unable to find any indication of where things are going wrong.
Expected Behavior
There is no "Bad Gateway" error, the HTTP service is available through Pangolin.
Workaround
Create an internal AAAA DNS entry for the target IP and point Pangolin to that. This indicates to me that the issue is caused by some component not parsing the target address correctly - I assume some component expects the aforementioned brackets around the IPv6 address and fails because they're missing.
@LaurenceJJones commented on GitHub (Mar 22, 2026):
Surprised the healthcheck are working.
This will be fixed once https://github.com/fosrl/pangolin/pull/2667 is released.