Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Latest post by nicholas on Monday, 19 February 2024 07:19 CST
Hi,
after upgrading to Akeeba Solo 8.1.2 I cannot login to Akeeba Solo.
After introducing my credentials and clicking login I'm redirected back to login with no error messages or similar.
I cannot see error messages in the error_log file either
I have tried with different browsers and a clean session with no success.
Any ideas what can I do?
Best!!
This is weird. I can login just fine on mine.
Can you please try deleting everything inside your tmp folder, and clear the browser cookies for your Solo installation? I am wondering if your problem is a stuck session issue.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi Nicholas,
sorry for the delay. I missed the email notification.
I have removed everything in the tmp folder and cleared my session but still cannot login. Any ideas that could help me debug the issue?
Thanks!!
Open Solo/assets/private/config.php.
Check the live_site key. It should be empty. If not, you may have a discrepancy between the hostname reported by the web server and the configured hostname which would invalidate the login cookie.
Finally, in that file, check the dbdriver, dbhost, dbuser, dbpass, dbname, and prefix keys. The first one should be either Mysqli or Pdomysql (note the first letter is capital). The other keys are your database connection information. If Solo cannot connect to the database it will show the login page, but it will be unable to log you in.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi Nicholas,
thank you very much for your reply.
I have been playing around a little bit, and it seems the issue had to do with my server configuration. Not sure why but switching the session.save_path location to the default session location suggested by Plesk, made the trick.
Best!!
Ah, that would totally do it. If the session save path in your PHP configuration is not writeable by the user PHP runs under, or is getting cleared every so often logging in will fail. I didn't think about it because if you set up Solo in an environment like this it tells you, during installation, and lets you set up an alternative session save path.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.
Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!