Repository navigation
Bad peer port config #416
Description
Hi, I just finally found the root cause of an ongoing but ephemeral issue and it turned out to be this same port being used by all peers. The port does need to be specified for the server config, but if all peers are set to have the same port then it can introduce issues with NAT. In my case, the server is running in a data center and when two peer/client devices are on the same remote network, they are constantly trying to clobber each other by trying to use the same port to handshake with the server (first established wins and the second exhibits weird behavior while it keeps attempting the handshake).
Since peer-to-peer is explicitly not supported per your README, the easy solution to this is just to remove this line and allow clients to choose their own random port.
Cheers
Activity
github-actions commentedon Jul 21, 2026
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
cmjordan42 commentedon Jul 21, 2026
Also a work-around note in case someone with the same problem finds this before it's addressed... this is merely the default config. You are able to specify your own peer config (with the port unspecified) and this config will not be used.
LinuxServer-CI commentedon Aug 21, 2026
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
cmjordan42 commentedon Aug 21, 2026
No activity because repo owners are inactive? I dunno... why close a useful report
LinuxServer-CI commentedon Sep 21, 2026
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.