• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Weird Wordpress/PHP error behavior on new Plesk/CentOS7 install

ItsDan

New Pleskian
Server operating system version
CentOS Linux release 7.9.2009 (Core)
Plesk version and microupdate number
18.0.46
I'm having some very strange issues after trying to migrate a Wordpress site from one Plesk install to another. It's a fairly large site so I've been doing so manually by zipping/moving/unzipping the files and moving the database myself. Both are on CentOS7, both are the latest Plesk, both are running PHP 7.4.30, both have comparable PHP settings shown in plesk.

When I've finished moving the site I'll be met with a critical error. Checking the logs I see:
AH01071: Got error 'PHP message: PHP Fatal error: Uncaught ErrorException: is_readable(): open_basedir restriction in effect. File(/dev/urandom) is not within the allowed path(s): (/var/www/vhosts/{site}/:/tmp/) in /var/www/vhosts/{site}/httpdocs/wp-includes/class-phpass.php:73

When I pull up that line I see this:
if (@is_readable('/dev/urandom') &&
($fh = @fopen('/dev/urandom', 'rb'))) {
$output = fread($fh, $count);
fclose($fh);
}

So it seems like the @ error suppression operator is being ignored and instead throwing a fatal error? I tried to fix this issue by adding that path to the basedir restriction but then another error occurred which also should have been suppressed. And again these errors didn't occur on the previous install. Resolving that error led me to an issue where a E_USER_DEPRECIATED message from Elementor was also treated as a fatal error.

For the life of me I cannot find a setting mentioned anywhere regarding depreciation warnings being treated as fatal errors, or enabling/disabling the @ suppression operator. I see something where in php8 it wont' silently fail anymore, but again this is PHP 7.4.31.

Any guidance or suggestions are appreciated.
 
Kindly ignore, PEBKAC, another developer had haphazardly registered an error handler that was causing the items to be logged as fatal errors. Why this didn't occur on the old hosting I'm not entirely sure, but one mystery down.
 
Back
Top