[GH-ISSUE #639] Port conflict #512

New issue

Closed

opened 2026-02-27 02:01:59 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 02:01:59 +03:00

Owner

Originally created by @fletchette on GitHub (Jan 20, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/639

Hey all
I'm trying to run a second Source server (TF2), but the console is giving me a port unavailable (27005).

The port config is like this -

Server 1
port="27015"
sourcetvport="27020"
clientport="27005"

Server 2
port="27017"
sourcetvport="27022"
clientport="27005"

Why is the clientport giving an issue? (isn't that just the port the client connects from?)
Does that mean I should change the client port for the second server?
Can I have the same port and sourcetvport for both servers?

Originally created by @fletchette on GitHub (Jan 20, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/639 Hey all I'm trying to run a second Source server (TF2), but the console is giving me a port unavailable (27005). The port config is like this - **Server 1** port="27015" sourcetvport="27020" clientport="27005" **Server 2** port="27017" sourcetvport="27022" clientport="27005" Why is the clientport giving an issue? (isn't that just the port the client connects from?) Does that mean I should change the client port for the second server? Can I have the same port and sourcetvport for both servers?

kerem closed this issue

2026-02-27 02:01:59 +03:00

kerem commented

2026-02-27 02:02:00 +03:00

Author

Owner

@UltimateByte commented on GitHub (Jan 20, 2016):

Hey dude !
Try changing the client port : surprise ! It works ! :p
Yes you have o change it too !
The first port is the queryport, sourcetv is sourcetv, and client port is used by clients, so it's not only an outgoing port.

@UltimateByte commented on GitHub (Jan 20, 2016): Hey dude ! Try changing the client port : surprise ! It works ! :p Yes you have o change it too ! The first port is the queryport, sourcetv is sourcetv, and client port is used by clients, so it's not only an outgoing port.

kerem commented

2026-02-27 02:02:00 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jan 21, 2016):

I believe it is only outgoing. However if one server is already using a port a second server cannot use it as well.

@dgibbs64 commented on GitHub (Jan 21, 2016): I believe it is only outgoing. However if one server is already using a port a second server cannot use it as well.

kerem commented

2026-02-27 02:02:00 +03:00

Author

Owner

@fletchette commented on GitHub (Jan 21, 2016):

Ok, thanks to both of you.

@fletchette commented on GitHub (Jan 21, 2016): Ok, thanks to both of you.

kerem commented

2026-02-27 02:02:00 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:53:20 +03:00

[PR #512] [MERGED] fix mistake #3114