Global login rejected, bad token

Dutchrai · Post by **Dutchrai** » Wed May 31, 2006 4:38 am

See title. I keep getting this message, then usually get kicked of the server. My password and userid are both correct. Can't "/unregister", can't use "/identify passwd" (these always seem to be disabled). I bypassed my firewall completely as well.

Any bright ideas?

Destroyer1313 · Post by **Destroyer1313** » Wed May 31, 2006 12:55 pm

Yeah, Its been going on for a while now... it started with the server
moving, that was when it was most noticeable.
Usually the problem is a bad connection or a
poor server. when you start BZFlag,look at the
chat window at the bottom of the screen and it says "Error, could
not talk with list server" you should check the connection and make
sure BZFlag can acces the internet. When you connect to
a server and it says "ERROR: DID NOT GET TOKEN" I think
it is a problem with the server. Usually if I close bzflag
and try to get back in it works, or playing on a different server
can pass the time. Usually, if a server isn't accepting me,
I play on a different server and then come back to that one.
If you REALLY, REALLY want to play on a certain server,
then attach something to your callsign, such as;

"Destroyer1313" becomes "Destroyer13133"

usually people dont notice this minor change.

Heh, are you sure you type the password in right? I always
have to remind myself to get it right. I don't know if any of this will help,
but I hope it does!

Dutchrai · Post by **Dutchrai** » Thu Jun 01, 2006 4:01 pm

Lol...yeah, sure I got it right (even have had my password reset to be sure). Tx for the tips though. Anyway, I am always having this problem, no exceptions. Restarts and all matter not, my connection of 2gb should be ok too, plus I am getting it with nearly every server. Weird. On a new account I have the same problem too (just had to try).

Whatever the reason, for the moment I am unable to play on servers that require global login.

JeffM · Post by **JeffM** » Thu Jun 01, 2006 4:23 pm

a couple things people forget.

1) global login does NOT USE /IDENTIFY or /REGISTER. It never has, never will. That is why they are disabled for servers that do global login only. Do not put your password in a chatbox ever. If you do, you have just given it to the server owner. Your callsign and password are put in the fields in game, nowhere else. The global login is done by your client and the list server, so the game server does not ever get your password.

2) if you have a caching proxy server at your ISP ( many many people do ) you may have login problems. If you are geting bad tokens then it means your ISP did not return the current web page from the list server, but a cached version of it. This means that you got an old token, that is indeed BAD. The simplest thing to try and fix this is to have your game use port 81 to talk to the list server, most ISPs will not cache that.

Just open your config, find the line that says "#set list http://my.bzflag.org/db" and just take off the # and put :81 after the .org.

3) if you have problems geting to the list server, make sure that if you have firewall software, it is set up to let bzflag send out web requests on port 80, just like a browser, it's how we talk to the list server.

Dutchrai · Post by **Dutchrai** » Fri Jun 02, 2006 3:11 am

Jeff, you're my hero!!!

Solution was to add the :81 behind the org. Darn ISP

Tx man.

themself? · Post by **themself?** » Fri Jun 02, 2006 2:54 pm

I'm having the same problem, but which configuration should I open, and where?

A Meteorite · Post by **A Meteorite** » Fri Jun 02, 2006 3:01 pm

themself? wrote:I'm having the same problem, but which configuration should I open, and where?

On Windows it is located here:

Code: Select all

My Documents\My BZFlag Files\2.0\config.cfg

Open that in NotePad and find "#set list http://my.bzflag.org/db" Replace it with:

Code: Select all

set list http://my.bzflag.org:81/db

(that's just taking off the pound sign and add :81 after .org)

Hope that helps!

themself? · Post by **themself?** » Fri Jun 02, 2006 3:16 pm

Had a few problems with that (realised I didn't take the # out

)

FIXED, THANKS!

Dutchrai · Post by **Dutchrai** » Fri Jun 02, 2006 3:59 pm

Since we're on the topic, is there any reason why this solution should not be standard in the configuration file?

A Meteorite · Post by **A Meteorite** » Fri Jun 02, 2006 4:34 pm

Dutchrai wrote:Since we're on the topic, is there any reason why this solution should not be standard in the configuration file?

Well, not everyone needs it...

And if everyone used it the ISPs may start blocking port 81.

chandler583 · Post by **chandler583** » Fri Jun 02, 2006 7:18 pm

OH NO! We don't want our ISPs blocking port 81, then we would never play bzflag.

I'm on one of those faster dial-up @52KBs connections and I haven't had any problem with lag, or getting a bad token. However, when I move to a computer with 5.5MBs, I have lag out the wazzo!

dgdog · Post by **dgdog** » Sun Dec 10, 2006 2:56 am

I havent been able to ID myself for months. Editing config, removing # sign (and maybe adding :81) to set list http://my.BZFlag.org:81 in config has given me + sign/ problem solved, thnks

Official forums for BZFlag.org

Global login rejected, bad token

Global login rejected, bad token

edit config.cfg worked for me