Is your feature request related to a problem?
The Status page network diagram currently only visualizes HTTP Proxy rules. Stream Proxy (TCP/UDP) entries are completely absent from the diagram, making it impossible to get a unified overview of all active proxy configurations in one place.
Describe the solution you'd like
Display Stream Proxy rules in the network diagram on the Status page, alongside HTTP Proxy rules. Each Stream Proxy entry could be represented as a distinct node (e.g., different color or shape to differentiate it from HTTP rules), showing:
- The listening port
- The target address and port
- Protocol (TCP / UDP / both)
- Active connection count (if available)
Why this matters
Users who rely on Stream Proxy for game servers or other TCP/UDP services currently have no way to see those tunnels in the status overview. A unified diagram would make it much easier to audit what is exposed and what is active without navigating to a separate menu.
Describe alternatives you've considered
Manually checking the Stream Proxy menu — functional but not a substitute for the at-a-glance overview the diagram provides.
Additional context
No existing issue or discussion appears to have requested this specifically. The diagram already handles multiple HTTP upstream nodes cleanly, so extending it to include Stream Proxy nodes seems like a natural and incremental addition.
Is your feature request related to a problem?
The Status page network diagram currently only visualizes HTTP Proxy rules. Stream Proxy (TCP/UDP) entries are completely absent from the diagram, making it impossible to get a unified overview of all active proxy configurations in one place.
Describe the solution you'd like
Display Stream Proxy rules in the network diagram on the Status page, alongside HTTP Proxy rules. Each Stream Proxy entry could be represented as a distinct node (e.g., different color or shape to differentiate it from HTTP rules), showing:
Why this matters
Users who rely on Stream Proxy for game servers or other TCP/UDP services currently have no way to see those tunnels in the status overview. A unified diagram would make it much easier to audit what is exposed and what is active without navigating to a separate menu.
Describe alternatives you've considered
Manually checking the Stream Proxy menu — functional but not a substitute for the at-a-glance overview the diagram provides.
Additional context
No existing issue or discussion appears to have requested this specifically. The diagram already handles multiple HTTP upstream nodes cleanly, so extending it to include Stream Proxy nodes seems like a natural and incremental addition.