1 gerardp Mar 27, 2020 22:56
Today I did an auto-upgrade System>Maintenance>Auto Upgrade
And ran into the same trouble as I have had before all over again.
However, this time I was able to fix it myself.
With my provider, the 500 error screen suggests that there are either badly set file permissions, or a problem with .htaccess.
If your site was running properly before, .htaccess ought not to be the problem, however, file permissions on the install folder are; at least in my case.
The install folder had today - as before - the wrong file permission settings: 775 instead of 755
For the problem to go away, you have to set the Install folder permission to 755 and all the file permissions to 644.
The easiest way to do this is through CPanel > File manager.
Once done, you can reload yoursite.com/install/index.html (or index.php) and will probably get a 503 error (site in maintenance)
This happens because the install script gets aborted, so the site is not taken automatically out of maintenance mode.
To take the site out of maintenance mode you need to rename the file umaintenance.html in the conf folder to _umaintenance.html
After that, you ought to be able to access the install folder and run the index.php script to update the DB and finish the install without further problems.
Hoping this helps (at least someone)
3 amoun Mar 28, 2020 10:07
4 gerardp Mar 29, 2020 04:54
You're always argumentative, Francois, and it's really tiring.
There is no step 4 and no file permissions are asked for.
Just trying to give people who go through this a hand, because nobody has EVER unequivocally answered this, least of all you.
5 amoun Mar 29, 2020 08:06
Hi @gerardp I suppose the note @fplanque has refered to is only in the manual @ https://b2evolution.net/man/upgrade-file-options and, as you said, is not asked for during the upgrade.
My query would be ~ Why does this happen during an auto upgrade and not only on the Debian example given, I say would as I'm not currently looking for an answer :)
6 fplanque Mar 29, 2020 21:29
It is in the more recent releases, it has been specifically added to address the problem described here.
I am providing this info for other people who may land here and may not need a more complicated solution than to enter the file permissions required by their specific host in the appropriate fields.
@gerardp you provided no version info
7 gerardp Apr 01, 2020 17:15
I did not provide version info, because I have been running into this problem for at least two years now, and have sometimes postponed upgrading because of it.
But, just for the sake of it, I'm running 6.11.5 stable, and now I have figured it out, will update on a more regular basis.
- Smile -
Did you enter the correct file permissions at step 4 here:?