• 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.

Issue Plesk firewall

Dmytro

Dmytro

Regular Pleskian
Server operating system version
Rocky Linux 8.7
Plesk version and microupdate number
18.0.48
Hi. I get strange problem.
Here is my plesk firewall settings:

Screenshot_18.jpg

If I make server reboot - it unreachable after reboot, I can't connect using ssh, ping shows all packets as lost and etc.
So after some research I'm connecting using IP KVM and running command:
Code: 
service psa-firewall restart

And all works again.
Why?
 
You must log in or register to reply here.

Similar threads

I
Question Plesk firewall and preventing clashes with firewalld
Replies
5
Views
2K
iainh
I
Z
Issue Firewall stopped working after update to Plesk Obsidian v18.0.77 on Debian 11.11
Replies
12
Views
6K
Kaspar
K
Azurel
Issue MariaDB 11.8.8: STRICT_TRANS_TABLES suddenly enabled after reboot AlmaLinux 9.7 → 9.8
Replies
2
Views
706
Azurel
Azurel
Azurel
Input AlmaLinux8to9 upgrade leaves Plesk in broken state with insufficient service checks and recovery guidance
Replies
2
Views
694
Azurel
Azurel
I
Resolved Preventing bot brute force probes against Postfix/SMTP
Replies
5
Views
2K
iainh
I
Back
Top