"Connection Failed After 10 Retries

[Bluehawk 0]

Every time i go to join JB this happens. It started happening a couple does ago out of nowhere. pls halp kthnx <3

[Rayne 4478]

Probably because you have a pink desktop you homo. 

[centran 4457]

a traceroute will not fully complete due to how we have our firewalls setup.

 

Usually the 10 retry error is due to there not being a server where you are trying to connect. Are you joining by your favorites? Sometimes the port will change on our end by accident and this can cause problems. With new persistent favorites thing valve added this shouldn't be a problem but your favorite list may have gotten messed up. For instance, trying to connect to port 27016 instead of 27015. Have you tried to open the game console and type connect jb.joinsg.net

 

Please try that and see if it works.

[GaryTheSnail 220]

I have the same problem and the solutions suggested by centran never worked for me. I never found a working solution so good luck.

[centran 4457]

I have the same problem and the solutions suggested by centran never worked for me. I never found a working solution so good luck.

 Post or PM me your IP. ipchicken.com

[Bluehawk 0]

a traceroute will not fully complete due to how we have our firewalls setup.

 

Usually the 10 retry error is due to there not being a server where you are trying to connect. Are you joining by your favorites? Sometimes the port will change on our end by accident and this can cause problems. With new persistent favorites thing valve added this shouldn't be a problem but your favorite list may have gotten messed up. For instance, trying to connect to port 27016 instead of 27015. Have you tried to open the game console and type connect jb.joinsg.net

 

Please try that and see if it works.

Thanks man! I joined through console and it worked.

[driz 2626]

i need all of you who have ever previously encountered an issue before to post if you have the issue again. I made two fixes last night and need to know if its resolved.

[iRecOver 1]

This happend sometimes to me, but not anymore, seems like it's fixed.

[driz 2626]

This happend sometimes to me, but not anymore, seems like it's fixed.

<sarcasm>thanks for the helpful post.</sarcasm>

[Clamps 4783]

This happend sometimes to me, but not anymore, seems like it's fixed.

 

 

<sarcasm>thanks for the helpful post.</sarcasm>

Got your back Driz,

 

[driz 2626]

anyone still seeing this issue?

[GaryTheSnail 220]

It hasn't happened to me in a week I think so thanks for the fix. If it happens again I will post here.

[Ttocsick 0]

I'm having a similar issue, anytime I go to load into the server whether it's from the browser or console it says Disconnected from the session. I can connect to the WCS server just fine, seems to be just an issue with the jb server. 

Tracert: http://imgur.com/ahWaTpM

 

Works now.

[driz 2626]

The traces don't help, that is the expected trace. Post your console messages please

[Popsicle_Ninja 34]

i got this last night at like ummm 12-2 in the morning trying to connect to surf

[driz 2626]

you got what? console error screenshots please. nothing you guys are posting helps us in any way. as far as im concerned, without something to help me troubleshoot servers this is all problems on the client side.

[GaryTheSnail 220]

Got it again, it happened immediately after I tried to use the command sm_invis2, dont know if that is just a coincidence.

Tried to look up command say as if it were a variable.Tried to look up command say as if it were a variable.Connecting to public(173.234.237.52:27015) ...Retrying public(173.234.237.52:27015) ...Retrying public(173.234.237.52:27015) ...Retrying public(173.234.237.52:27015) ...Retrying public(173.234.237.52:27015) ...Retrying public(173.234.237.52:27015) ...Retrying public(173.234.237.52:27015) ...Retrying public(173.234.237.52:27015) ...Retrying public(173.234.237.52:27015) ...Retrying public(173.234.237.52:27015) ...Connection failed after 10 retries.] connect 173.234.237.54:27016Connecting to public(173.234.237.54:27016) ...Retrying public(173.234.237.54:27016) ...Retrying public(173.234.237.54:27016) ...Retrying public(173.234.237.54:27016) ...Retrying public(173.234.237.54:27016) ...Retrying public(173.234.237.54:27016) ...Retrying public(173.234.237.54:27016) ...Retrying public(173.234.237.54:27016) ...Retrying public(173.234.237.54:27016) ...Retrying public(173.234.237.54:27016) ...Connection failed after 10 retries.

[driz 2626]

Gary thank you, looking into it. Anyone else who had an issue please post the same logs Gary submitted. <br /><br />Gary is this server in your favorite? Can you remove it and re-add it

[GaryTheSnail 220]

Yes, it is in my favorites. I'll try it when I get back to my computer

[Face 1910]

Been having this issue for the past few weeks on and off.  Seems like every time a small CSGO update is released I have the issue for 2-3 days then it has stopped (I don't know if this correlates with you guys fixing it).

Just tried to connect via console 3 separate ways and here is what I got:

] connect war3.joinsg.netConnecting to public(173.234.237.51:27015) ...Server using 'public' lobbies, requiring pw no, lobby id 18600001bdf93a1RememberIPAddressForLobby: lobby 18600001bdf93a1 from address 173.234.237.51:27015GameTypes: could not find matching game type "".CSysSessionClient: Cannot join lobby, response 2!] connect wc3.joinsg.netConnecting to public(173.234.237.51:27015) ...Server using 'public' lobbies, requiring pw no, lobby id 18600001bdf93a1RememberIPAddressForLobby: lobby 18600001bdf93a1 from address 173.234.237.51:27015GameTypes: could not find matching game type "".CSysSessionClient: Cannot join lobby, response 2!] connect 173.234.237.51:27016Connecting to public(173.234.237.51:27016) ...Retrying public(173.234.237.51:27016) ...Retrying public(173.234.237.51:27016) ...Retrying public(173.234.237.51:27016) ...Retrying public(173.234.237.51:27016) ...Retrying public(173.234.237.51:27016) ...Retrying public(173.234.237.51:27016) ...Retrying public(173.234.237.51:27016) ...Retrying public(173.234.237.51:27016) ...Retrying public(173.234.237.51:27016) ...Connection failed after 10 retries.

If you need any more info feel free to ask...

[centran 4457]

Well the last command wont work cause you put in a port of 27016 which normally is not the port the game server runs on.

 

As for why it didn't work the first time it could be one of two things. Either your client was not updated yet or the server needed to be restarted due to stale session cookies. If that happens then you need to contact staff and inform them of the problem as other people are probably experiencing the same thing. Unfortunately, it is a weird bug that sometimes only effects a couple of people and if the server is populated at the time we may hold off on restarting it till population falls.

[Face 1910]

a traceroute will not fully complete due to how we have our firewalls setup.

 

Usually the 10 retry error is due to there not being a server where you are trying to connect. Are you joining by your favorites? Sometimes the port will change on our end by accident and this can cause problems. With new persistent favorites thing valve added this shouldn't be a problem but your favorite list may have gotten messed up. For instance, trying to connect to port 27016 instead of 27015. Have you tried to open the game console and type connect jb.joinsg.net

 

Please try that and see if it works.

 

Well the last command wont work cause you put in a port of 27016 which normally is not the port the game server runs on.

 

As for why it didn't work the first time it could be one of two things. Either your client was not updated yet or the server needed to be restarted due to stale session cookies. If that happens then you need to contact staff and inform them of the problem as other people are probably experiencing the same thing. Unfortunately, it is a weird bug that sometimes only effects a couple of people and if the server is populated at the time we may hold off on restarting it till population falls.

I used 27016 based off of the first post I quoted.  I don't really understand ports that well but I didn't know if it would change anything.

My friend was having the same issue and he got in a bit ago so hopefully whatever the issue was is fixed now.