• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Backup Manager unable to back up banned IP addresses

miagg

New Pleskian
After upgrading to AlmaLinux 9 and Plesk 18.0.80, backup manager shows this warning on every backup.
Code:
Unable to back up banned IP addresses. Error: f2bmng failed: ERROR:__main__:Failed to get packages by files: package manager returned 5 lines instead of expected 3. Command was ['/bin/rpm', '-qf', '--queryformat', '%{NAME}\\n', '/etc/fail2ban/jail.conf', '/etc/fail2ban/jail.d/plesk.conf', '/etc/fail2ban/jail.local'] and returned exit status 1. Your package system might be inconsistent. Please check it for issues with 'plesk sbin pum --check --full'.

I tried reinstalling fail2ban by following instructions on the link below, but as another user says it did not fix the problem.
https://support.plesk.com/hc/en-us/...-Jails-in-Fail2Ban-f2bmng-failed-ERROR-f2bmng
 
Hi, @miagg . Kindly run the command from the error and confirm if it returns any warning/errors related to the keys:

Code:
plesk sbin pum --check --full
 
Gi @Sebahat.hadzhi,
Yes I've run it at least twice.
Here is the output:

Markdown (GitHub flavored):
2026-08-23 21:25:00 INFO: pum is called with arguments: ['--check', '--full']
warning: Signature not supported. Hash algorithm SHA1 not available.warning: Could not load key gpg-pubkey-24098cb6-58875d52
warning: Signature not supported. Hash algorithm SHA1 not available.warning: Could not load key gpg-pubkey-24098cb6-58875d52
2026-08-23 21:25:03 INFO: pum completed successfully
 
So, it seems like there's indeed an issue with the GPG keys of a repository, which is not necessarily a Plesk issue.

Please try identifying the repository in question:

Code:
rpm -qi gpg-pubkey-24098cb6-58875d52

Once you identify the problematic repository, please try importing a new key.
 
Thank you @Sebahat.hadzhi,
I ran the above command and found out I had an obsolete Grafana SHA‑1 GPG key after the almalinux8to9 migration.

I solved it by running the following:
Bash:
rpm -e gpg-pubkey-24098cb6-58875d52

curl -fsSLo /root/grafana.gpg https://rpm.grafana.com/gpg.key
rpm --import /root/grafana.gpg

I'm not sure if this will solve the backup manager warning though. I triggered a custom backup, and I will report once it finishes.
 
Back
Top