I have just uploaded one of my sites to a public server and I can’t log in into the panel. When I log in with correct credentials I get redirected back to the log-in page WITHOUT any error message. If I use incorrect credentials I get an error message.
I also tried a fresh kirby 2.2.3 installation and had the same problem after installing. I also tried an older verision of kirby (2.1 I think) and it worked without a problem.
All my frontend pages are working, I’m using a vanilla kirby .htaccess file. I get no js errors in the console when I try to log in. I can’t log in with all browsers.
Thats Interesting for Couple months i had the Same Problem whit 2.2.3, after who i have create my account, i have delet it and creat it again and it works
I turned the debug on with
c::set(‘debug’,true)`
but I don’t get any php errors nor can I see any in error logs (last entry from december!)
I definitely see that a cookie is being created (and I also debugged the process with printouts all the way until the cookie and the redirect after) for the user to be logged in, so it seems that the bug is in the filter somewhere, I’m trying to find where the filter is being applied to deal with it there…
Other people had a very similar issue before.
The solutions there are related to the session store and the Varnish cache proxy. Maybe some of that applies to your server as well?
I don’t think so. I don’t know if its the best way to check but there is a site that you can check for the chace on it - and it says it’s not working. http://www.isvarnishworking.com/
Also, is the login problem is only happening with the latest version of kirby, does that mean anything?
I have a site running with an old version it’s working fine.
The weirdest thing is that a month ago I also had a site using kirby 2.2.3 running on this server and it worked fine (this is my staging server, my client already bought 3 kirby licenses and we’re planning on 2 or 3 more).
I’m still playing with kirby trying to figure what’s happening, will keep yall updated.
I’m looking at the cookie and the session file.
It looks like in the cookie there is a variable called kirby_session and it’s equal to the session ID. BUT thep PHPSESSID is different.
So is php trying to load the new PHPSESSID everytime? I don’t have much experience with sessions… so does anyone know how that works? get around it?