Search results

Thank you - To clarify, is there a delay or a throttled delivery of when the major updates are actually applied? All of our server panels show the 18.0.29 release as ready to install but none of attempted to actually install it automatically.

With Plesk Obsidian, should automatic updates be expected for larger version upgrades such as 18.0.28 Update #3 to 18.0.29 or do larger version jumps need to be manually initiated? If it is expected to be automatic, which of these little fellas would be responsible for enabling that...

Another consideration might be to use the Linux screen command to account for unforeseen drops in Internet connectivity.

What kind of disk space was available at restart?

Yes, many mirrors were very slow to pick it up so either it was a question of waiting a week or manually updating the package.

‪CentOS Linux 7.7.1908 Version 17.8.11 Update #85 No CloudLinux Plesk Onyx for Linux returns this error for Yum and Plesk update commands: 403 packages excluded due to repository priority protections Exception: Failed to solve dependencies: plesk-php56-imagick-3.1.2-centos7.20042209.x86_64...

Are you able to share your solution?

Are you taking advantage of OPcache? OPcache can behave strangely with inefficient or error-ridden code which in some scenarios could possibly negate its benefits.

Thank you for your follow-up! Here are the answers to your questions: - PHP errors using the Plesk PHP 7.2 handler were written to the site's error log and not the /var/log/plesk-php73-fpm/ error file - "Add PHP 7.3 handler support via Plesk GUI" (this refers to adding the PHP 7.3 handler via...

here are some examples of code that was previously only written to the site's PHP error log and is now being written to the handler's log instead:

TITLE: Plesk Onyx 17.8 PHP 7.3 Handler Logs All Levels to Syslog PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: 17.8.11 Update #71, CentOS Linux 7.7.1908 PROBLEM DESCRIPTION: Following addition of the Plesk PHP 7.3.10 handler version via the Plesk components tool, all PHP errors that use it...

Indeed, same issues here on the same OS/Plesk versions!

While a recent upgrade of ten servers went off without a hitch, it's still a good idea to take a snapshot or backup image of those servers and kick off the process after work hours to help minimize any potential downtime should you run into an issue that's not quick or easy to recover from.

Not a bug

In the stock Plesk install, mail for a given domain will first attempt a local delivery regardless of where your mail is located unless it's deactivated. In your case you shouldn't need to modify the /etc/postfix/main.cf to get mail to properly deliver to MX records outside of your domain name...

If it's just a limited number of sites and doesn't involve email, it might a consideration to zip the files in each of their respective document roots, copy those over, and then bring over databases. Other than that, it's a bit more of a process to get the old server up and running; any chance...

For the record, Plesk Forums are generally oriented towards a community-based approach to support issues. The forums are not really officially support channels in the same sense as a Plesk support ticket which specifically focuses on your unique setup while the forums tend to be supported by...

403 headers can be returned from scripts and with your server IP appearing in the log as it does in your snippet, it sounds like a a script running on the server that is causing that entry to be written . You would likely see a bunch of other requests for this at the same time, all with 403...

Just be aware that you might need to monkey with converting htaccess rules when running Nginx

The underlying cause of this is not so much related to your server but rather that your index.php script or your application is not sanitizing inputs. Inputs passed to sites or pages may be legitimate or nefarious in nature so while there are tools that run at the server or CDN level to scan...