Resolved CS:GO - bhop - i can't connect to bhop

Status
Not open for further replies.
Taco

Taco

Active Member
Joined
May 12, 2018
Messages
386
Bug Reports​

What application are you reporting this issue on?

CS:GO
​

Short description of the problem (255 char limit)

i can't connect to bhop
​

What server are you reporting this issue on?

bhop
​

Please describe the issue in as much detail as possible.

i can not connect to the bunny hop server.
​

What should be happening instead?

connect me to b hop
​

Please describe how to replicate the bug in as much detail as possible

it seems to be only me and only for this server
​

Any extra info we may need to know

here is my console when trying to connect
] connect 74.91.124.34:27015
**** Unable to localize '#DemoPlayback_Restart' on panel descendant of 'HudDemoPlayback'
**** Unable to localize '#DemoPlayback_Back' on panel descendant of 'HudDemoPlayback'
**** Unable to localize '#DemoPlayback_Pause' on panel descendant of 'HudDemoPlayback'
**** Unable to localize '#DemoPlayback_Slow' on panel descendant of 'HudDemoPlayback'
**** Unable to localize '#DemoPlayback_Play' on panel descendant of 'HudDemoPlayback'
**** Unable to localize '#DemoPlayback_Fast' on panel descendant of 'HudDemoPlayback'
**** Unable to localize '#DemoPlayback_Next' on panel descendant of 'HudDemoPlayback'
**** Unable to localize '#Panorama_CSGO_Spray_Cursor_Hint' on panel 'RosettaInfoText'
ChangeGameUIState: CSGO_GAME_UI_STATE_MAINMENU -> CSGO_GAME_UI_STATE_LOADINGSCREEN
**** Panel has fill-parent-flow for height, but isn't in a flowing down or up layout
PNG load error Interlace handling should be turned on when using png_read_image
Connecting to public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Communications with routing cluster 'pwg' restored.
Communications with routing cluster 'shb' restored.
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Retrying public(74.91.124.34:27015) ...
Connection failed after 30 retries.
​
 
Re cache csgo then try again. This usually occurs when you connect and download add-ons not compatible with our server plugins. I think..
 
Taco, try a tracert to the server from your cmd prompt.

C:\Users\mille>tracert 74.91.124.34

Tracing route to d-74-91-124-34.ded-machine.premium-chicago.nfoservers.com [74.91.124.34]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 <1 ms <1 ms <1 ms 192.168.1.1
3 22 ms 28 ms 18 ms XXXlightspeed.anarmi.sbcglobal.net [75.38.XX.X]
4 18 ms 18 ms 18 ms 71.151.244.5
5 30 ms 32 ms 28 ms 12.123.7.70
6 28 ms 26 ms 27 ms cgcil403igs.ip.att.net [12.122.133.33]
7 26 ms 26 ms 26 ms chi-b21-link.telia.net [213.248.87.253]
8 27 ms 25 ms 25 ms chi-b22-link.telia.net [62.115.141.170]
9 25 ms 25 ms 25 ms telia-3.e11.router2.chicago.nfoservers.com [66.85.80.253]
10 26 ms 28 ms 25 ms d-74-91-124-34.ded-machine.premium-chicago.nfoservers.com [74.91.124.34]

Trace complete.
 
Dont post #1-3 as that's your public IP. But we need to see how far your packet is getting. Because the retries mean your packets aren't getting to the server. If it was server-side issue, I think it would give you a response about not letting you on
 
umm it only had

C:\Users\Andrew>tracert 74.91.124.34

Tracing route to d-74-91-124-34.ded-machine.premium-chicago.nfoservers.com [74.91.124.34]
over a maximum of 30 hops:

1 6 ms 6 ms 7 ms Fios_Quantum_Gateway.fios-router.home [Insert my ip]
2 13 ms 10 ms 10 ms d-74-91-124-34.ded-machine.premium-chicago.nfoservers.com [74.91.124.34]

Trace complete.

C:\Users\Andrew>
 
What if you did the normal CSGO servers?

C:\Users\mille>tracert 74.91.113.113

Tracing route to d-74-91-113-113.ded-machine.premium-chicago.nfoservers.com [74.91.113.113]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 <1 ms <1 ms <1 ms 192.168.1.1
3 18 ms 18 ms 28 ms lightspeed.anarmi.sbcglobal.net [75.xx.xxx.x]
4 18 ms 19 ms 18 ms 71.151.244.5
5 27 ms 31 ms 32 ms 12.123.7.70
6 34 ms 24 ms 31 ms cgcil403igs.ip.att.net [12.122.133.33]
7 26 ms 26 ms 27 ms chi-b21-link.telia.net [213.248.87.253]
8 26 ms 26 ms 25 ms chi-b22-link.telia.net [62.115.141.170]
9 25 ms 25 ms 29 ms telia-3.e11.router2.chicago.nfoservers.com [66.85.80.253]
10 28 ms 25 ms 26 ms d-74-91-113-113.ded-machine.premium-chicago.nfoservers.com [74.91.113.113]

Trace complete.
 
C:\Users\Andrew>tracert 74.91.113.113

Tracing route to d-74-91-113-113.ded-machine.premium-chicago.nfoservers.com [74.91.113.113]
over a maximum of 30 hops:

1 10 ms 10 ms 7 ms Fios_Quantum_Gateway.fios-router.home [My ip]
2 10 ms 9 ms 9 ms d-74-91-113-113.ded-machine.premium-chicago.nfoservers.com [74.91.113.113]

Trace complete.

C:\Users\Andrew>
 
Ok now open command prompt and do this:
telnet 162.248.92.58 27024

If it goes to a blank black screen, that's normal. It means you connected.
 
Status
Not open for further replies.

Latest posts

Back
Top