NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Real IP when using NPM Streams
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
- 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
Describe the bug
I have an OVH proxmox server with a Debian 11 VM (NAT network).
Basically i simply installed npm in my VM and using Streams i redirected port 9987 UDP
to my home teamspeak ip.
It works, i can connect my OVH VM ip:port and it redirects me to my home teamspeak server.
The problem is that when i check my user ip inside teamspeak, it shows my OVH VM ip.
I want to be able to see my real ip.
Nginx Proxy Manager Version
v2.10.4 (latest)
Expected behavior
I expect to see my real ip in teamspeak user connection info, not OVH VM ip.
Operating System
Debian 11
Any possible solution?
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 with the Streams configuration and Nginx stream proxy behavior for UDP port 9987, then reproduce the setup using the Debian 11 VM, OVH NAT network, and TeamSpeak backend described in the report. Done means determining whether the original client IP can be shown in TeamSpeak and documenting the supported configuration or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100