Author Topic: Fixing a server having "---" ping (Read 1907 times)

Port · December 30, 2013, 01:28:23 PM

Before the UPnP update, all servers had a ping and a connection message like this:

Connecting to 1.2.3.4:28000 Sending challenge request...

And that it's. Now about half of running servers have "---" ping and get stuck on an arranged challenge request (why in the world was this added, by the way?) while connecting.

Recently this has been happening to my server and I have no clue why.

✓ Port 28000 forwarded to the correct local IP on UDP.
✓ UPnP disabled in Blockland and in the router itself (I've also tried with it enabled in the router).
✓ Blockland executable and port 28000 on UDP explicitly allowed in firewall settings.
✓ No kind of third-party antivirus or firewall software.
✓ No kind of "Hamachi" tunneling software or similar.

(no, this is not related to the authentication issues going on at the time of this post)

Ad Bot · Advertisement

Advanced Bot · December 30, 2013, 01:36:00 PM

Yea, I have been having the same issues as well with mine. I have done most of those and it still has a ping of "---" and I sometimes get stuck on arranged challenge request.

Lugnut · December 30, 2013, 01:36:34 PM

Can you join the not --- servers?

Port · December 30, 2013, 01:36:49 PM

About 75% of people say they can't connect to my server and get stuck.

UnRegistered · December 30, 2013, 01:37:44 PM

I've encountered this as well, sometimes it varies for no reason. I have a lot of issues for when people try to connect to my dedicated server. They've been on the low for a bit (quite a few people were able to connect). The fix is that you need to refresh the master server to rejoin but most people don't know that you can do that to fix it, so thus they bypass the server as down.

Lugnut · December 30, 2013, 01:40:25 PM

Can you post a server sided console segment from when the server auths and when players try to join?

Port · December 30, 2013, 01:42:25 PM

Binding server port to default IP UDP initialized on port 32612 Starting client steam authentication... Engine initialized... Received stats and achievements from Steam Authentication: SUCCESS Executing config/client/avatarColors.cs. Loading object base/data/shapes/player/m.dts Destroying NET Server Exporting server prefs... Starting Internet Server Binding server port to default IP UDP initialized on port 28001 Initializing UPnP... -------------------- List of UPNP devices found on the network : desc: http://192.168.1.1:2555/upnp/805da163-6cca-38dd-8269-e279abb01f89/desc.xml st: urn:schemas-upnp-org:device:InternetGatewayDevice:1 desc: http://192.168.1.1:2555/upnp/805da163-6cca-38dd-8269-e279abb01f89/desc.xml st: urn:schemas-upnp-org:device:InternetGatewayDevice:1 desc: http://192.168.1.1:2555/upnp/805da163-6cca-38dd-8269-e279abb01f89/desc.xml st: urn:schemas-upnp-org:device:InternetGatewayDevice:1 Found valid IGD : http://192.168.1.1:2555/upnp/89695e5e-ad41-3aa5-8baf-92a4e4e2513d/WANIPConn1.ctl Local LAN ip address : 192.168.1.2 ExternalIPAddress = 93.160.176.206 Internal IP:Port = 192.168.1.2:28001 External 93.160.176.206:28001 UDP is redirected to internal 192.168.1.2:28001 -------------------- ... Got connect request from IPX:00000000:000000000000:0 net name = Port Connection established Connected successfully, killing other pending connections AUTHCHECK: Port = LAN client -> internet server, auth with server ip Add-Ons/GameMode_Quake/src/maps/map.cs (0): Unable to find function grammarJoinJSONList Direct load Add-Ons/Quake_Lava_Temple/save.bls, 3, , 2, 1 LOADING BRICKS: Add-Ons/Quake_Lava_Temple/save.bls (ColorMethod 3) Steam Lobby Created: 109775243220112053 Steam Lobby Joined: 109775243220112053 lobby enter torquescript callback, yourlobby: 1 this is our lobby have a server connection! Auth Init Successfull: Port CADD: 8369 local +- bl_id = 46342 +- AUTO SUPER ADMIN (ID same as host) Posting to master server

Yes, UPnP is disabled, despite it initializing it for some reason..?

Port · December 30, 2013, 01:43:12 PM

Err, that was a console.log from a different setup (thus port 28001), hang on.

Lugnut · December 30, 2013, 01:43:47 PM

What about when someone else fails to join?

Port · December 30, 2013, 01:46:22 PM

I don't really have any logs (started executable as client without hosting a server last time) from this instance currently and I can't get any due to blockland.us being dow nright now.

Lugnut · December 30, 2013, 01:48:28 PM

Well I dunno then, but if you fix it on your own be sure to post what you did.

Azure · December 30, 2013, 02:54:16 PM

This has been here for as long as I have been on Blockland (BL:ID 26544, around 2-3 years), but not as severe as this. All I can tell you is that using an RTB server will eliminate this problem, probably because they are professional servers. Even crappy routers will always get less than 100 ping on them.

Port · December 30, 2013, 03:09:54 PM

Quote from: Azure on December 30, 2013, 02:54:16 PM

This has been here for as long as I have been on Blockland (BL:ID 26544, around 2-3 years), but not as severe as this.

Started when UPnP was added.

Quote from: Azure on December 30, 2013, 02:54:16 PM

All I can tell you is that using an RTB server will eliminate this problem, probably because they are professional servers.

How is that supposed to be helpful?

Quote from: Azure on December 30, 2013, 02:54:16 PM

Even crappy routers will always get less than 100 ping on them.

Your router doesn't have anything to do with this bug or ping (not significantly, anyway), though?

blocky151 · December 30, 2013, 07:38:15 PM

This is really weird, if all those things you mentioned are good, that shouldn't be happening..