Failed to start session after moving to server with PHP 7.1 and 7.2 Topic is solved

[Larion476]

My site was running on Joomla 9.1 with PHP version 7.0.32 and I getting the message that I should enable PHP 7.1.

When I did I was getting a blank page with the word error.

I contacted my ISP and moved the site to a new server where PHP 7.1 an 7.2 are present.

Now my site will not load I get the following error:

Warning: session_start(): Failed to read session data: user (path: /opt/alt/php72/var/lib/php/session) in /home/hilair/public_html/libraries/joomla/session/handler/native.php on line 260
Error: Failed to start application: Failed to start the session

Regardless of which version of PHP I load.

I had to change the password of the cPanel when I moved to the new server.

[Webdongle]

How did you move your site ?
If you did it manually did you edit the configuration.php paths and database details ?
viewtopic.php?f=714&t=793531 please

[Larion476]

I did not move the site. Paths and data base details are the same.
I checked with phpMyAdmin the database is there.
I checked the configuration.php the only thing I am not sure of is the entry
public $Secret

[sozzled]

Instructions for use: viewtopic.php?f=621&t=656394&start=120#p3543744

[Webdongle]

I did not move the site. ...

But you said

...
I contacted my ISP and moved the site to a new server where PHP 7.1 an 7.2 are present.
...

Please ... which of your two statements is the correct one. Also FOR the UMTEENTH time of asking viewtopic.php?f=714&t=793531 please!!!

[Larion476]

Sorry about that.

What I meant is that my whole site was moved from one server to another, but the structure of the folders/files is exactly the same.

Also all the databases were transferred. I can access all of them.

I have several subdomains, the one not using Joomla I can access.

One subdomain,I called sandbox to try stuff, is using Joomla and I have the same problem.

[Webdongle]

The database Host will be different on the new server will it not? If so then it needs to be edited in the configuration.php file. Also the database user (although the same name) will have had to be created? If so then it might not have the correct Privileges.

Please run viewtopic.php?f=714&t=793531 and post the results here.

[Larion476]

Before all this I took a backup of the site yesterday with Akeeba.

Now I created a new subdomain a new database and a new user and restored the site using the7.2 version of PHP. Apart from a couple of issues with a plugin and a module that are using deprecated command I managed to get back my site.

If I use PHP 7.0 or 7.1 I get the error again.

Questions for you. Can I restore my site to the original location? What would happen to the existing files and tables?

[Webdongle]

The database is your site ... all the files do is put/get data to/from your database and display them in the browser.

[Per Yngve Berg]

The error is on the server. The path /opt/alt/php72/var/lib/php/session is not writeable.
Where php saves it's session is set by the save.session.path directive in php.ini

[Larion476]

SOLVED with the help of my ISP.
He figured out that because of tighter security the new MySQL version did not like the user password I was using (too weak) and was creating a random one, which I had no clue what it was.
My solution was to modify the configuration.php file with the user name and password I was using in the new subdomain. I also gave that user access to the original DB. Et voila!

[Webdongle]

Your Internet Service Provider helped you sort out the Host site ... are you using the free Hosting some ISP's provide?

[Larion476]

No I am paying for my hosting

[VietPublic]

SOLVED with the help of my ISP.
He figured out that because of tighter security the new MySQL version did not like the user password I was using (too weak) and was creating a random one, which I had no clue what it was.
My solution was to modify the configuration.php file with the user name and password I was using in the new subdomain. I also gave that user access to the original DB. Et voila!

Thanks, Worked
Just because of the wrong username and password connecting to the database