Search results

In that case it looks more like one of your PHP scripts is used for sending email spam, e.g. a contact form that has a auto-responder to the given email address including some form fields or the website has a malware infection or is just not update and has open doors. You could track it down...

This user cannot be deleted, because it is the system user of the subscription used for login via ssh/ftp(s)/sftp. Furthermore all PHP handlers and interpreters are running as that user. You can only change the user name but not delete it. More information can be found here...

Here is the patched policy rule for the problem mentioned: /etc/amavis/conf.d/99-warden The application firewall of the forum does not let me post the new sql statement. I did attach it as pdf file. The original query was just extended in the "where" clause by another "or" condition including...

With some little changes to Warden's sql_select_policy config parameter aliases will use the policy settings of the main mailboxes associated to them. We are now doing internal tests and when all works fine we will present a patch for all interested ones.

Hello at all Plesk Warden Anti-spam and Virus Protection users, at the moment we are facing an outgoing spam problem caused by not blocking detected spam messages if mail was sent to an email alias address. Steps to reproduce: -> create an email address e.g.: mail@domain.com -> create an...

Hello @maartenv , see also: Postfix Configuration Parameters - for reject_unknown_client_hostname and reject_unknown_reverse_client_hostname: 450 4.7.25 Client host rejected: cannot find your hostname, [IP] - for reject_non_fqdn_sender: 504

Hello @ssmmdd , Amavis with SpamAssassin and ClamAV should not be seen as primary tool to fight incoming spam. On our servers 80% of all spam is already filtered out before with an appropriate Postfix configuration. reject_non_fqdn_sender + reject_unknown_client_hostname +...

I did inform the Plesk team in the Bugreport about the restart issue already: Forwarded to devs - PHP extension sodium is suddenly not bundled anymore We are using the dedicated PHP FPM application only. We cannot say, if the normal PHP FPM application was also affected. When another PHP update...

Hello, we did experience the same problem with our Nextcloud instances because of the latest Plesk PHP updates. Try to restart your PHP handlers. This did help in our case. More info can be found here: Issue - No sodium extension for PHP 7.4.30 FPM

We did install the new update on two of our servers. The result was headache again. Maybe our documentation can help others that run into the same problems. Both servers are using Debian 10 and did get the previous Plesk PHP Updates from 14th of June 2022 already and were repaired accordingly...

PHP Updates - 17 June 2022 Linux The Sodium extension is now dynamic for PHP 7.4, 8.0, and 8.1 again. (PPPM-13609) Argon2 passwords are working now on Debian 9 “Stretch” for PHP 7.4, 8.0, 8.1. (PPPM-13611) https://docs.plesk.com/release-notes/obsidian/change-log/ We can close here.

It seems the issue is already addressed as PPS-13031. An KB article was also published: https://support.plesk.com/hc/en-us/articles/6077118452370 See thread: Issue - No sodium extension for PHP 7.4.30 FPM In our case we also had to manually restart all PHP handlers to get the problem fixed.

We had the same problems e.g. with Nextcloud instances (login was not possible anymore / error messages). It seems after the upgrade the PHP handlers need to be restarted. This solved our login problem mentioned. Some servers also hat the mentioned sodium.ini leftovers.

Username: TITLE PHP extension sodium is suddenly not bundled anymore PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.44 Update #3, Debian 10.12, x86-64 PROBLEM DESCRIPTION Without any notice in the changelog the sodium PHP extension was removed from the latest...

Without any notice in the changelog the sodium PHP extension was removed from the latest Plesk PHP releases: PHP Updates - 14 June 2022 Updated PHP 8.1 to version 8.1.7. Updated PHP 8.0 to version 8.0.20. Updated PHP 7.4 to version 7.4.30. For some servers we could freeze the upgrade in the...

At the moment the update policy of Plesk is getting more and more headache. Nearly with every new feature release 18.0.x new bugs on existing functionalities are introduced. So we already changed our own update plan to wait at least for "Update 1" + no serious problems are submitted in the...

Some resellers have dozens of servers and thousands of clients. There is no time for manual intervention or monitoring. In our case we also have SLAs about the backup availability. We cannot even allow to have one missing day of backups. And we are just a small player. I really wonder why this...

Let's hope a patch will be available soon or at least before the release of 18.0.42. Right now this critical bug prevents us from updating our servers.

Plesk Obsidian 18.0.40 Update 2 did mark the package finally as outdated.

Any changes made to main.cf will be overridden on a regular basis. There is also a feature request since many years: Allow customization of /etc/postfix/main.cf