[SOLVED] Server Lost Client Token
|
04-12-2015, 05:41 AM
(This post was last modified: 04-12-2015 07:46 AM by Inquizitor.)
Post: #1
|
|||
|
|||
[SOLVED] Server Lost Client Token
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 Code: 12-04-2015 01:18:02.565 INFO Communication request queued: "login" 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. |
|||
04-12-2015, 06:53 AM
Post: #2
|
|||
|
|||
RE: Server Lost Client Token
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. :-)
|
|||
04-12-2015, 07:35 AM
Post: #3
|
|||
|
|||
RE: Server Lost Client Token
All is well again! Thank you.
|
|||
04-12-2015, 09:30 AM
Post: #4
|
|||
|
|||
RE: [SOLVED] Server Lost Client Token
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.
|
|||
« Next Oldest | Next Newest »
|
Possibly Related Threads... | |||||
Thread: | Author | Replies: | Views: | Last Post | |
Windows b5 client bugs | sellyme | 53 | 53,984 |
11-12-2012 09:51 PM Last Post: wfps_105 |
|
Bugs and feature for 2.0b5 - Mac OS X client | bman4789 | 3 | 5,634 |
10-11-2012 06:17 PM Last Post: smitmartijn |
User(s) browsing this thread: 1 Guest(s)