HTTP 500 Error upgrading 4.1.9 to 4.2.6

HTTP 500 Error upgrading 4.1.9 to 4.2.6

by Barry Andrews -
Number of replies: 3
Hello

I am trying to upgrade my moodle installation using cpanel for our provider.
The site meets all the pre-requesits for 4.2.6, however when I upgrade our existing 4.1.9 installation I simply get an HTTP 500 error and cannot use the site. The only solution is rolling back the backup.

I have tried setting the config file permissions and the folder permissions but this has no effect.

As the site is updated through cpanel, I have minimal control over the whole system.
PHP is version 8.1

Average of ratings: -
In reply to Barry Andrews

Re: HTTP 500 Error upgrading 4.1.9 to 4.2.6

by Ken Task -
Picture of Particularly helpful Moodlers
500 errors don't tell us much cept it's a major server config issue ... not just config of Moodle.

Are you using Softaculous to upgrade?

Go to Site Admin -> Server -> Environment check
Update component
Set drop down list for Moodle version for 4.2 - all greens?

Have you checked additional plugins for 4.2 compatibility - themes are plugins.

Check https://moodledev.io/general/releases/4.2 for server requirements.

Does your cPanel have Terminal and Git icons?

Doesn't hurt to mention hosting provider and what plan you are using to lease - plans determine memory/space, etc.

'SoS', Ken

In reply to Ken Task

Re: HTTP 500 Error upgrading 4.1.9 to 4.2.6

by Barry Andrews -
Hello Ken

Thanks for the response.
My server uses Installatron to install the app.
It shows the 4.2.6 as being okay to install.

I looked at the link you gave and found everything is okay except:
I found it needs Maria DB 10.6.7, but web server has 10.5.22.

Yes, it has terminal and git, host is AOBO and is just a basic plan, but has plenty of disk space and RAM.

I don't control when Maria DB this is updated, so will need to contact the AOBO and see what they say, hopefully it is just this.
In reply to Barry Andrews

Re: HTTP 500 Error upgrading 4.1.9 to 4.2.6

by Ken Task -
Picture of Particularly helpful Moodlers
You should also ask your provider to contact Installatron makers and inform them.
One thing of which you should be aware ... Installatron creates a moodledata directory inside the moodle code and uses hidden ... check your config.php file for path to moodledata and you should see something like .safowfnvasasedata ... see the 'dot' in front?

I mention that to avoid confusion should you decide to use documented methods of upgrading your moodle code.   Since you have terminal and git, the best way is really via command line and git.

Matter of fact, you might also do this:
Click terminal and at the prompt in the terminal screen, type:
uname -an [ENTER]
That's shows what operating system running.
To exit terminal, type: exit [ENTER]

Also remind you to check all addons for compatibility ... if using a theme other than boost or classic.   Moodle's environment check checks only core ... not addons.  Ditto for Installatron.

https://moodle.org/plugins/
https://moodle.org/plugins/browse.php?list=category&id=3

'SoS', Ken


Average of ratings: Useful (1)