Cantr II Discussion Forum

I've started to have log in errors after I've logged in and try to view a character. I enter in my ID and password correctly, then it takes me to my player page, then when I click on a character I get logged out with the message:

I've tried several times to view a character, and every time I get logged out with the error. I also get logged out if I try to view my player settings, or even if I try to log out from my player page. Any ideas?

I have seen this before too. As far as I could tell, the cookies weren't being set for some reason. It was finally "solved" after installing Firefox (it had this problem in both Internet Explorer and in Chrome, both with cookies being allowed).

I figured it was something cookie related. Strange though since it has worked just fine for a long time. I was using Chromium in Ubuntu. I moved over to windows and it works just fine now. I will take another look later and see if I can figure out something more specific in case other users have the same problem.

I had this one time and computer restart helped. I checked this "from inside" and this was very strange webbrowser behaviour - was not setted cookies, if their expired time was in nearest 12h.

I've been having this problem a lot, especially on mobile/mini browsers such as the one on my Nintendo 3DS (which runs an Opera-based browser, I believe.)

And what helped? Restart?

psychowico wrote:And what helped? Restart?

Nope, restart didn't work. I cleared my history and cookies, I turned it off and back on, I called it vulgar names... and it still doesn't work for Cantr.

Uh, I not have idea what can be wrong with this..

I still have the same issue on my cellphone and I don't know if it would be possible to install another browser on it. The sad part is the old login system used to work on it, while the cookie-based system doesn't. Cookies are accepted but maybe there's something wrong with them. Maybe it could print the contents of the cookie in the bottom of the page so that you could compare if it's different on a cellphone than on a PC.

I haven't had the problem again myself. Just out of curiosity, does your computer and cellphone have the same date/time set on each?

Cellphone clock is two minutes too fast but that shouldn't affect things.

Okay, I'm currently browsing on my 3DS at a laundromat and Cantr is working perfectly. It seems like the problem (at least for me) is tied to using my home Wi-Fi connection and my 3DS. My roommate (Auryn), however, can use Cantr from his 3DS perfectly, and it works fine on a computer and our home Wi-Fi. I'll try from my 3DS when I'm done with laundry.
EDIT: Have returned home, where Cantr from 3DS is working fine. *shrugs*

lol I believe that are some problems with you client apps.

psychowico, this isn't some place to up your post count. Please keep information relevant (ie. if you want to claim it is their client apps, specify why you believe so).



A question to those having this problem, do you all access Cantr from multiple devices or just one?

I've noticed, over a period of time, that in most cases of frequent login errors, it's been via a wireless device, such as mobile phone or a shared wi-fi connection, etc.
Wireless connections have a tendency to 'lose' the connection for split seconds here and there, which causes some devices to 'auto-clear' or 'forget' some cookies, which may well be cause of logging you out.
Some websites have a workaround for it, remembering to keep you logged in for a short period of time, so that any unreliable connection can be countered with a more reliable login session. I wonder if that would be possible in this case.

If we wanted to find this out for sure, it would be an idea to set up a poll for some basic research, but I'd like that to be arranged by one of the staff here.
Hopefully it would include;
frequent login errors from a wired desktop pc/wired laptop
frequent login errors from a cellphone/ipad
frequent login errors from a wireless pc/laptop
frequent login errors from another wireless/wi-fi device

This would help identify what sort of connection/device is causing the most problems. Hopefully we could learn enough to put it right, too.