Search results

Please compare and show the output of: # yum info MariaDB-server # yum info --disableexcludes=all MariaDB-server

grep -r exclude /etc/yum* should show you. Unless this is due to DNF module exclusions (which I don't believe it is).

Remove the exclude from your DNF configuration. Yes.

Yes, currently it's not supported for Mailman. There's a chance it won't be supported for Mailman 2 at all.

dkimpy

ARC signing is enabled by default. So this effectively does nothing out of the box. Can be disabled via plesk bin settings -s mail_arc_sign=false plus repair mail.

At this time - no. However, "Allow signing outgoing mail" should be enabled.

Please run the following command and paste it's entire output here: bash -x /usr/lib/plesk-9.0/mariadb_repo_setup --mariadb-server-version mariadb-10.11 --skip-maxscale --skip-check-installed

Yes, recent versions (including the one shipped with Plesk Obsidian) do this. Seems like a misuse of fail2ban. Why not just use firewall for that (if these bans are effectively persistent)?

fail2ban in default configuration doesn't work well with non-iptables firewalls anyway. Loosing bans from fail2ban is not critical, since all of the bans are temporary anyway. And recent versions of fail2ban persist them, so if you need to restore lost bans, just restart the fail2ban service...

You may have slow iptables (e.g. due to virtualization). Increasing the confirmation timeout via panel.ini might help.

There's quite a few system firewall implementations out there. Plesk Firewall extension works only with iptables or those that provide compatibility layer for iptables (such as nft). Other implementations (such as firewalld) should be turned off before enabling Plesk Firewall.

Firewall 2.0.2 was released. It includes a number of improvements to address activation issues you've encountered. See also its changelog for instructions on increasing confirmation timeout in case simple extension update will not resolve the issue in your case. The root cause in each...

To the original posters: Firewall 2.0.2 was released. It includes a number of improvements to address activation issues you've encountered. See also its changelog for instructions on increasing confirmation timeout in case simple extension update will not resolve the issue in your case. CLI...

Applying firewall configuration should be an interactive operation. Otherwise one risks completely cutting off access to the server for the user. After adding your customizations show a notification in Plesk that suggests the user to go to the Firewall page, review the rules, and apply the...

@danami, I'm sure other Plesk devs already communicated this to the Warden devs, but I'll duplicate this information here, just in case. This is an internal utility. Nobody should use it directly or pay attention to whatever is written in its help, except for the Firewall extension developers...

Please update to the latest Plesk 18.0.40.

Fix for the issue has been released. Please update your Plesk (e.g. via plesk installer update).

Of course, there are cases when package system must be temporarily broken to achieve the needed result. Plesk packages removal is generally not one of them.

Please don't use --nodeps or even rpm for removal. This way you don't guarantee package system consistency. Just use yum remove instead and review other packages (if any) that would be removed.