Search results

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

I don't know that I would call 0.9.6 out-dated. From Downloads - Fail2ban as of today: experimental : fail2ban-0.10.x (Working up to production environments but not quite there yet!) stable : fail2ban-0.9.4 very-stable : fail2ban-0.8.14

Indeed the same issue is still popping up on CentOS 7.4.x systems running 17.5.3 here as well (no manual fix attempted). Looks like the Plesk folks updated their bug report about five hours ago: cron.daily/asl failing with "/usr/bin/find: invalid argument `+' to `-ctime'"

Same issue here on Cent OS Linux 7.4 installs!

What a bugger of a problem. Anecdotally it sounded like it had something to do with the way that iptables gets gracefully stopped (along with Fail2Ban) and even though iptables is restarted Fail2Ban does not get restarted. Hopefully this thread receives some additional insight that could help...

Possibly related or not, this was just updated: Unable to open phpinfo() in Plesk: Error: Unable to retrieve information about the PHP configuration

This isn't quite what you're looking for but just to get the party started while you look into your piping question, you could set it up without piping for now (POP3/IMAP Setting Guide - osTicket) and use a "Scheduled Task" within Plesk to hit the cron script for accuracy and control.

Are you sure that this is an html page? Check the error log for that site in Plesk and you may find a fatal PHP error that is causing this.

You might need to do some research but at this point in the process, it's difficult to ascertain that Plesk is the cause based purely on your CPU graphs. If you have mod status installed but not configured (in this case we'll assume CentOS), go to /etc/httpd/conf.modules.d and add this file if...