Upgraded c-panel from 65 to 78 and now I cannot access my forum

[1kether1]

Hello,

We upgraded our C-panel software from 65 to 78 and now our VB forum running 4.2.3 Patch Level 1 does not work. (We get an "HTTP ERROR 500" when we try to access the site now.) I'm not sure what to do to get things working again. Please help.

Thank you,
Kether

[Mark.B]

Check your php version. vBulletin 4.2.3 will only work with php 5.4 or php 5.6.
If you are running php 7.0. or 7.1 then you'll need to upgrade to vBulletin 4.2.5.
If you are running php 7.2 then you will need to ask your host to downgrade php to 7.1, as vBulletin 4 is end of life and won;t work with php 7.2.

[1kether1]

Hi Mark, Thank you for the quick response. How would I upgrade to 4.2.5 if I am unable to access the ACP?

[Mark.B]

Hi Mark, Thank you for the quick response. How would I upgrade to 4.2.5 if I am unable to access the ACP?

You don’t need to.

Backup database
Upload all new files
Run /install/upgrade.php in the browser. Append that to the end of the root forum path.

[1kether1]

I checked and we are running php 5.6 and c-panel is version 78. Should we upgrade php to 7.0 and then update the forum to 4.2.5? I'm not sure which to do first - or if this will solve the issue since we are running php 5.6 and the forum is 4.2.3. Thank you for your help, Mark. I sincerely appreciate it.

[Mark.B]

I checked and we are running php 5.6 and c-panel is version 78. Should we upgrade php to 7.0 and then update the forum to 4.2.5? I'm not sure which to do first - or if this will solve the issue since we are running php 5.6 and the forum is 4.2.3. Thank you for your help, Mark. I sincerely appreciate it.

php 5.6 should be fine with vBulletin 4.2.3.

It could be an old add-on breaking the admincp.

Can you check the server logs (your host can help here if needed) an d post back with the actual error?

[1kether1]

php 5.6 should be fine with vBulletin 4.2.3.

It could be an old add-on breaking the admincp.

Can you check the server logs (your host can help here if needed) an d post back with the actual error?

I found what it was, Mark. It was memcache. I commented it out in the config file and had to re-enable ini_set and that fixed the issues. I still need to go ahead and upgrade to the latest version, but all is working again. Thank you for your help.

[Wayne Luke]

If you're running Memcache, you will need to purge the cache after upgrading.

[1kether1]

If you're running Memcache, you will need to purge the cache after upgrading.

Thank you,Wayne.