Search results

Igor, Thank you for the provided information, the update went out like a charm. Florian.

Igor, The file that handles the updates for spam assassin is: vi /etc/cron.d/sa-update However in order to configure the version that is compatible with Plesk this automatically wipes the update code in this file and replaces it with # This task was disabled by psa-spamassassin package on a...

Hi there, I am just wondering if there is any possibility to update the SpamAssassin package which comes with Plesk 12 from 3.3.1 (obsolete version built in 2010) to the latest one which at the moment is 3.4.1? Many thanks for your answers or thoughts.

Login as root user on your Linux server and run "yum update". All the available libraries will be updated without your intervention. The latest versions available for PHP are 5.6.17 and 7.0.2.

Trialotto, Thank you for your replies and all the help you provided. I haven't managed to apply your last thoughts (complete uninstall of PHP via epel/Plesk and reinstall) because the last PHP 7.0.2 update applied via yum solved all the issues. I am not sure what the problem was but...

Also, there is a slight chance that PHP was updated from 7.0 to 7.0.1 via yum update (before the MU from Plesk appeared). Am not sure if this might raise an issue or not.

@trialotto I have followed your steps suggested above to uninstall and reinstall PHP 7.0. Unfortunately the problem remains the same and the error for all WP instances remains the same. 2016-01-13 12:54:00 Warning 79.112.44.78 (104)Connection reset by peer: mod_fcgid: error reading data from...

All the websites are working perfectly with PHP 5.6.16 (FPM) but none work with PHP 7.0.1 (FPM). However, they used to work with PHP 7.0 (FPM). Am not familiar with the autoinstaller commands to uninstall/reinstall PHP 7, can you help us with this aspect? Many thanks!

Trialotto, Thank you for your reply and excuse my late answer. A couple of comments about my issues 1. first of all, everything was working absolutely perfect on PHP 7.0, the issues have arised only when PHP was updated to 7.0.1 (via Plesk MU) 2. i cannot run any PHP command under 7.0.1, not...

After updating Plesk from 12.5.30 #15 to #18 (which also updated PHP 7.0 to 7.0.1), all the WordPress websites hosted on the server are displaying a 500 error. The logs are similar in all the situations 2016-01-05 10:42:20 Error 86.124.185.88 Premature end of script headers: index.php Apache...

Thank you for this update. A couple of comments (tested this on 3 different servers, all with Plesk 12.5.30 #15): Updating multiple plugins in one shot still displays the following warnings but the update is completed successfully. Updating multiple WordPress instances works without any issues.

I have found more issues. After the WordPress updates from 4.3.1 to 4.4 were implemented, the security checking procedure within WordPress Toolkit also corrupted some rules of Apache and thus some files are not loaded anymore (for example the text editor inside WordPress). The error log is full...

Same issue here. Successfully upgraded 29 WP instances from 4.3.1 to 4.4 and the screen below is shown. Also, the update took enormous (around 1 hour) when normally this was performed in 2-3 minutes. The plugins and themes are not accessible anymore from WordPress Toolkit. OS ‪CentOS 6.7...

Negative, still waiting for a solution.

The "Check Security" procedure displays that all the WordPress instances are not secured (marked with a red exclamation sign) even if they were all secured before. After you click a "not secured" installation, the system displays that actually everything OK and marks that specific installation...

The log is store under /usr/local/psa/admin/logs/panel.log After several investigations with my support team: 1. there was one file with incorrect permissions [root@server ~]# stat /usr/local/psa/admin/sbin/mod_wrapper File: `/usr/local/psa/admin/sbin/mod_wrapper' Size: 17408...

Some extracts from the logs, maybe somebody can help me with a solution. Thanks! [2014-07-12 18:59:07] ERR [panel] Failed to parse response. Reason: Failed to read data from stream Process output: : 0: PMMConnector.php:708 PMMConnector->getResponse(object of type StreamXMLReader)...

Good evening, After a successful upgrade from 11.5.30 to 12.0.8 the Backup Manager cannot be accessed anymore. The system replies with: Internal error: Failed to parse response. Reason: Failed to read data from stream Process output: Message Failed to parse response. Reason: Failed to...

Just a notification, the bug is still present even after the latest update to MU #41.

I have the same bug on my server. It started after MU #39. OS CentOS 5.9 (Final) Panel version 11.5.30 Update #39