• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Wordpress Install Error

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 everyone,

This issue has been fixed, thanks for reporting it.
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
 
Hi Jan,

Can you tell us what error you are seeing exactly? Could you please also tell us what do you mean by "frozen"?
 
Hi Jan,
Hi, thank you for reply
Can you tell us what error you are seeing exactly? Could you please also tell us what do you mean by "frozen"?
"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 '.
 
Jan,

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.
 
Back
Top