Author Topic: Server could not verify Blockland ID.  (Read 1452 times)

My server has been rejecting loads of people with this message:
Server could not verify your Blockland ID.
Under the console log, it just says: Authentication failed for <player name> (IP <XX.XX.XX.XX>)

My firewall is disabled
My ports are properly forwarded
What do I do? I really want to host my server and I need help desperately. I know that this will probably receive less attention than pigeon stuff on the sidewalk but I need someone to help me.

Try to access auth.blockland.us on the network/machine that you are hosting with.

Try to access auth.blockland.us on the network/machine that you are hosting with.
That displayed the message auth.blockland.us on a otherwise empty webpage, which I assume is what it's supposed to do?
I can log onto the game and play on other servers no problem, it's just hosting that gets me.
Before I forget, here's the console.log with two connection attempts, one without trace(1) and one with trace.

Are you hosting the server on the same computer, or network, as your client?

Try connecting locally. If it's a single computer, just connect to 127.0.0.1, otherwise, connect to the local IP.

Are you hosting the server on the same computer, or network, as your client?

Try connecting locally. If it's a single computer, just connect to 127.0.0.1, otherwise, connect to the local IP.
Connecting locally works, but that's not the point. The problem is that people trying to connect over the internet cannot join because of that error.

I have had this same problem for about a year now and am wondering if anyone else can give some insight?

Try asking someone else to join the server. Have that person check their IP address and then compare that address to the one that shows up in your console log. The auth system works by sending the player's name and IP address to the auth server, and then the auth server replies YES if the IP sent matches the IP the auth server has stored for that player's last client authentication (This is why you get kicked out of servers if your IP changes while you have Blockland open). Auth will always fail if your server is receiving an IP address that is different from the real IP address of the person trying to connect, this might be caused by a non-transparent proxy server.

Try asking someone else to join the server. Have that person check their IP address and then compare that address to the one that shows up in your console log. The auth system works by sending the player's name and IP address to the auth server, and then the auth server replies YES if the IP sent matches the IP the auth server has stored for that player's last client authentication (This is why you get kicked out of servers if your IP changes while you have Blockland open). Auth will always fail if your server is receiving an IP address that is different from the real IP address of the person trying to connect, this might be caused by a non-transparent proxy server.
I tried joining Enn's server and got the issue

Try asking someone else to join the server. Have that person check their IP address and then compare that address to the one that shows up in your console log. The auth system works by sending the player's name and IP address to the auth server, and then the auth server replies YES if the IP sent matches the IP the auth server has stored for that player's last client authentication (This is why you get kicked out of servers if your IP changes while you have Blockland open). Auth will always fail if your server is receiving an IP address that is different from the real IP address of the person trying to connect, this might be caused by a non-transparent proxy server.
Assuming this is the problem, what can I do to fix it?

Seriously, does anyone know how to solve this issue?

it randomly fixed itself for me. this is an annoying ass problem thats for sure

ISP? I'm trying to narrow it down to a singular problem ATM

ISP? I'm trying to narrow it down to a singular problem ATM
I'm in Singapore, so you won't recognize my ISP. It's Singtel.

I'm in Singapore, so you won't recognize my ISP. It's Singtel.
Well, that just knocked the ball out of the park. It's a problem on CloudFlare's end, probably a caching error (like what happened with Steam)