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

Plesk Firewall

R

Ricardo1234

New Pleskian
Hi all,

I've noted virtuozzo adds the following firewall rules to my VM by default:
1) All tcp input for hi port allowed (32768-65535)
2) All udp input for hi port allowed (32768-65535)

Does anybody has got any idea why this happens? Is this a requirement so Plesk can run smoothly?
I did note when rule enabled HTTPS services runs faster. I am not a network expert by any means however i'm intrigued to why this is a "default" rule.

Thanks for you any feedback
Ric
 
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
Azurel
Question Could someone share their "ss -tulpn" output from AlmaLinux 9?
Replies
1
Views
437
Azurel
Azurel
Z
Issue Firewall stopped working after update to Plesk Obsidian v18.0.77 on Debian 11.11
Replies
12
Views
5K
Kaspar
K
first4it
Issue Docker containers unable to resolve DNS or access external network on Plesk Obsidian 18.0.76 Update #4 (Collabora / Nextcloud issue)
Replies
2
Views
3K
first4it
first4it
I
Resolved Preventing bot brute force probes against Postfix/SMTP
Replies
5
Views
2K
iainh
I
Back
Top