Search results

@Amadex disabling the entire EPEL repo isn't a solution. I recommend just adding the line exclude=ImageMagick* to the [EPEL] section in the file /etc/yum.repos.d/epel.repo for now. I'm sure that the Plesk devs will likely update the ImageMagick from their repo as the EPEL repo updated their...

No not yet. Remember that extension developers get new Plesk releases the same time as everyone else so we've only had access to it for less than a week. There are a number of issues that we've already identified in testing under Ubuntu 22.04 so they will have to be fixed before it's supported.

Yes you only want to use an exclude like exclude=ImageMagick* temporarily (the exclude applies to epel packages only). Apparently the reason the EPEL upgraded ImageMagick mid cycle like this was to fix a bunch of security vulnerabilities. Ultimately the permanent fix is for Plesk to build their...

@sergiomb Unfortunately --skip-broken will not work in this case. The only work around is to add the line exclude=ImageMagick-libs in the /etc/yum.repos.d/epel.repo file or via the command line using: dnf update --exclude=ImageMagick-libs

Normally I agree but with all the high level nftables exploits this year sometimes it's better to use something that's been around for a while: [oss-security] Linux kernel: CVE-2022-1015,CVE-2022-1016 in nf_tables cause privilege escalation, information leak [LWN.net]

nftables is used by default but you can still use iptables. You just have to install it using `apt-get install iptables` so this shouldn't be an issue for Plesk Firewall or Fail2ban.

Unfortunately spamassassin takes much more than just bayes training in order to configure it properly. (Which is why your spam scores are at 2.0). Spamassassin is extremely powerful but has a very high learning curve. I've been using it myself for almost 15 years and I'm still learning new...

The data is migrated. You just need to point it to the mailboxes .spamassassin folder. Remember by default bayes data is per mailbox. You were just checking the global settings. You need to use: sa-learn --dbpath /var/qmail/mailnames/example.com/user/.spamassassin --dump magic

Warden Anti-spam and Virus Protection 2.16 has been released. Advanced Queue Management, Debian 11 Support, and More! Announcement: Announcements - Danami

Here is another nice guide: https://linuxiac.com/centos-7-to-almalinux-8-migration-guide/ More about the ELevate project: https://almalinux.org/elevate I would love to see Plesk support this :)

I wouldn't think that is an issue. If I remember correctly Plesk is owned by WebPros HoldCo B.V. Amsterdam, Netherlands and WebPros itself is owned by CVC capital partners. Only some of the developers are based out of Novosibirsk, Russia.

@Peter Debik support.plesk.com is using Cloudflare so content is going to be sent from your servers closest Cloudflare server. Here are the ranges: IP ranges https://www.cloudflare.com/ips/ Datacenters https://www.cloudflarestatus.com/

If you guys are still wanting AbuseIPDB support we recently added it to the latest release of our Juggernaut Firewall extension: Announcements - Danami

Juggernaut Security and Firewall 3.02 for Plesk has been released. AbuseIPDB Suppport, New Blocklists and More! Announcement: Announcements - Danami

@BigD213 Make sure that you have downloaded the latest CLI product installer. I didn't have any trouble installing Plesk on Rocky Linux using it...

@tkalfaoglu Enable the powertools repo and it should fix this: # dnf --enablerepo=powertools install perl-Digest-SHA1

Sentinel Anti-malware 1.16 for #Plesk has been released. Third Party Signatures and More! https://www.danami.com/clients/announcements/128/Sentinel-Anti-malware-1.16-Released.html

Warden Anti-spam and Virus Protection 2.14 has been released. Third Party Signatures, AbuseIPDB Support, and More! https://www.danami.com/clients/announcements/126/Warden-Anti-spam-and-Virus-Protection-2.14-Released.html

The first thing that you should to is set proper outgoing sending limits. That way if an email account is compromised then you can limit the damage that the email account can do before you are alerted...

Yes I thought it should of worked (that's why I was scratching my head). I'm glad that you have it sorted.