19 replies to this topic

[DrN]

I'm able to setup a lobby properly and start a game. But once the game starts everyone is shown as not connected and there isn't any reporting system ingame. But tf2center has rcon access to my server, does anyone know what's wrong?

[Foxy]

Do you have a server IP or lobby number?

[MasterNoob]

When connected to your server, in dev console (~), type

rcon sv_logsecret

Tell us what it says...

[DrN]

When connected to your server, in dev console (~), type

rcon sv_logsecret

Tell us what it says...

 

This is set to 0

"sv_logsecret" = "0"

 - If set then include this secret when doing UDP logging (will use 0x53 as packet type, not usual 0x52)

 

 

 

Do you have a server IP or lobby number?

#142861 104.40.8.173:27015

 

I've tried forward ports 27000 to 27050 for both TCP and UDP and this didn't solve the issue. 

Edited by DrN, 28 June 2014 - 11:23 PM.

[Foxy]

[2014-06-29 00:22:24,580] Logline blocked from host: 104.40.8.173:1024 | only accepting from: 104.40.8.173:27015

 

Are you doing some weird port-forwarding on your end of outbound traffic?

[DrN]

[2014-06-29 00:22:24,580] Logline blocked from host: 104.40.8.173:1024 | only accepting from: 104.40.8.173:27015

 

Are you doing some weird port-forwarding on your end of outbound traffic?

 

The server I'm hosting on is a cloud computing service. Where ports need to be forwarded for outbound/inbound traffic, So I'm assuming that I need to allow traffic on port 1024? UDP/TCP?

[MasterNoob]

TF2C assumes it will receive logs from exactly the same host+port as specified during the Lobby creation. It doesn't matter whether that is port 1024 or 27015.

[DrN]

TF2C assumes it will receive logs from exactly the same host+port as specified during the Lobby creation. It doesn't matter whether that is port 1024 or 27015.

if that's the case port 27015 is open for both UDP and TCP and players can join the server without any issues. As well as rcon commands being issued from TF2C. Is there a specific port that needs to be forwarded for the server to send information to TF2C?

[MasterNoob]

Nope

Nope

[DrN]

Nope

Nope

 

if that's not the case any idea what is?

[Foxy]

Your server is running on port 27015, but logs are coming from port 1024. I'd suggest that either your server is really running on port 1024, or something is altering the packets to make them come from port 1024. What is the setup you have - is it a home router and home PC, or hosted VPS / hosted server?

[DrN]

Your server is running on port 27015, but logs are coming from port 1024. I'd suggest that either your server is really running on port 1024, or something is altering the packets to make them come from port 1024. What is the setup you have - is it a home router and home PC, or hosted VPS / hosted server?

I'm running the server from a vps cloud hosting service that provides a virtual public ip for usage and endpoints for ports I want to use. My server is running on port 27015 on the internal ip address and works fine for playing on with the public ip address on port 27015. 

 

So does that mean only the log packets are getting directed through port 1024, instead of 27015?

Edited by DrN, 30 June 2014 - 09:49 PM.

[Foxy]

It means outbound traffic from your server seems to be coming from port 1024. Your VPS host may be doing this so outbound traffic is routed via a proxy or something, but I'm not sure how to diagnose that fully. What's the VPS hosting company called?

[DrN]

It means outbound traffic from your server seems to be coming from port 1024. Your VPS host may be doing this so outbound traffic is routed via a proxy or something, but I'm not sure how to diagnose that fully. What's the VPS hosting company called?

The server is being hosted on a microsoft  azure cloud computing vm

[Foxy]

http://social.msdn.m...nly-udp-traffic seems to describe your problem. I don't think we can do anything to rectify it though.

[DrN]

http://social.msdn.m...nly-udp-traffic seems to describe your problem. I don't think we can do anything to rectify it though.

 

Wouldn't the solution be to just use 1024 as the game server port, then there wouldn't be a problem when accessing logs?

[MasterNoob]

 

http://social.msdn.m...nly-udp-traffic seems to describe your problem. I don't think we can do anything to rectify it though.

 

Wouldn't the solution be to just use 1024 as the game server port, then there wouldn't be a problem when accessing logs?

 

 

That would be very simple for you to test, wouldn't it? Create a 1v1 Lobby, ask a buddy to join and see if you see the connection status update...

[Foxy]

Need anything more from us on this?

[Kartoffel]

I'm having the same problem but I'm using tragicservers as my host.

 

74.91.125.85:27015 is my server. I'm using the direct IP after being told the dns reroute might be the problem, but that's shown it is not. The problem sprouted up just recently.

http://rc.tf2center.com/lobbies/167371

Edited by Kartoffel, 25 July 2014 - 02:32 AM.

[ninjaMooCow]

Tragic has fixed a bug in their configs since July.

 

I think this is UDP packet routing due to cloud server.  It is a serious corner-case.  I will set to pending user response, if no response within 24h I will close.