• 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 Fail2Ban don't init with Plesk Obsidian 18.0.21

E

Edu Membrillas

New Pleskian
I have a problem with this service. I have done two clean installations on two different servers and I have the same error. By default fail2ban was started, but stop it and now it is impossible to restart it. Any ideas?
 
What kind of error messages do you have? Any related details, logs, steps to reproduce?
 
It's solved.

The problem was the Jails, they were all activated and some generated conflicts. I have activated only the ones that Plesk brings by default

76414.png
 
You must log in or register to reply here.

Similar threads

Rendor9
Question Do I need to disable or uninstall UFW and Fail2Ban before installing Plesk Obsidian?
Replies
1
Views
866
Rendor9
Rendor9
K
Resolved Watchdog says Plesk Web Server down since 18.0.79
Replies
3
Views
603
King555
K
O
Issue LogBrowser, Fail2ban and SASL filter
Replies
0
Views
2K
OverWolf
O
L
Question Wordpress sites unable to access Plesk webstat page
Replies
1
Views
714
scsa20
scsa20
A
Resolved hosting update is failed: webstatmng: (ubuntu)
Replies
2
Views
780
TalkBuildHost
T
Back
Top