[SOLVED] Server Lost Client Token

[Inquizitor]

I suddenly can't pulse using the latest beta. App.log gives me the following errors, saying 'Server lost client token:'

Code:

12-04-2015 01:14:11.596 DEBUG Autopulse on keys:  10436
12-04-2015 01:14:15.037  INFO void __thiscall ClientCommunication::clientReLogin(void) Server lost client token, we need to login again.
12-04-2015 01:14:21.034  INFO Lost token 2 times in a row, assume server issues and back off.
12-04-2015 01:15:11.595 DEBUG Autopulse on keys:  10454
12-04-2015 01:15:15.090  INFO void __thiscall ClientCommunication::clientReLogin(void) Server lost client token, we need to login again.
12-04-2015 01:15:21.094  INFO Lost token 2 times in a row, assume server issues and back off.
12-04-2015 01:16:11.598 DEBUG Autopulse on keys:  10476
12-04-2015 01:16:15.036  INFO void __thiscall ClientCommunication::clientReLogin(void) Server lost client token, we need to login again.
12-04-2015 01:16:21.038  INFO Lost token 2 times in a row, assume server issues and back off.
12-04-2015 01:17:11.617 DEBUG Autopulse on keys:  10496
12-04-2015 01:17:28.673  INFO void __thiscall ClientCommunication::clientReLogin(void) Server lost client token, we need to login again.
12-04-2015 01:17:34.671  INFO Lost token 2 times in a row, assume server issues and back off.

---At this point, I logged off, logged back in and tried tried to reset my token.---

Code:

12-04-2015 01:18:02.565  INFO Communication request queued: "login"
12-04-2015 01:18:05.829  INFO void __thiscall ClientCommunication::clientReLogin(void) Server lost client token, we need to login again.
12-04-2015 01:18:11.827  INFO Lost token 2 times in a row, assume server issues and back off.
12-04-2015 01:20:26.960  INFO void __thiscall ClientCommunication::clientReLogin(void) Server lost client token, we need to login again.
12-04-2015 01:20:32.962  INFO Lost token 2 times in a row, assume server issues and back off.

Downgrading back to 2.5 seems to solve the problem, but 2.6 beta won't work, even after a reinstall.

I'll go back to 2.5 for a bit. I'm sure it's something server-side, but I figured I'd bring it to your attention.

[smitmartijn]

Server issue, is solved. No reason to go back, the whole login bit you saw was the improvement in the protocol, which makes sure it doesn't pulse until it has a proper connection. So that works. :-)

[Inquizitor]

All is well again! Thank you.

[smitmartijn]

Also, for anyone who's interested: the new protocol uses a login and a session token on the website before doing anything stats related (sending, resetting). The sessions are stored in a database which was down this night. Will make sure that it's redundant before the stable release.