Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread: CentOS2Alma discussion
Hi, I have also problem with update to Wordpress 4.1.1-84. I have two VPS and few working websites are frozen already and also websites with only Plesk Wordpress pre-installation. Plesk Panel 11.5.30 Update #48, last updated at Oct 24, 2014 03:46 PM Any help and advice?
Hi, Could you help me with Wordpress 4.1.1-90 error under Plesk? Before I have error 4.1.1-84 and frozen and lock 15 domains but last 24 hours this error was clean. Present I have still 5 domains frozen with Wordpress update
error 4.1.1-90. Any advice?
Regards
Jan
"Frozen" should be not working, just can't open websites. sorry. I got two type of message below when I "click" on "update to 4.1.1-90 now"
Best Regards
Jan
Error: No updates found
or
Error: Update failed: Non-zero exit status returned by script. Output stream: 'PHP Warning: require(/var/www/vhosts/special4you.co.uk/httpdocs/wp-load.php): failed to open
stream: No such file or directory in /var/www/vhosts/special4you.co.uk/httpdocs/wp-admin/upgrade.php on line 18 PHP Fatal error: require(): Failed opening required
'/var/www/vhosts/special4you.co.uk/httpdocs/wp-load.php' (include_path='.') in /var/www/vhosts/special4you.co.uk/httpdocs/wp-admin/upgrade.php on line 18 '. Error stream: 'PHP
Warning: require(/var/www/vhosts/special4you.co.uk/httpdocs/wp-load.php): failed to open stream: No such file or directory in /var/www/vhosts/special4you.co.uk/httpdocs/wp-
admin/upgrade.php on line 18 PHP Fatal error: require(): Failed opening required '/var/www/vhosts/special4you.co.uk/httpdocs/wp-load.php' (include_path='.') in
/var/www/vhosts/special4you.co.uk/httpdocs/wp-admin/upgrade.php on line 18 '.
This looks like a rare bug we've encountered a couple of times. Proper fix is pretty complicated, but we'll see if we can fix it in 12.1. Meanwhile I'd suggest you to contact our support if you need an immediate fix, and reference bugs PPP-10349 and APSI-1 for refund.