• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

glitch in Plesk 12.5 firewall setup/creation?

TomBoB

Silver Pleskian
Hi,

Plesk 12.5 MU#13 on CentOS 7.1 64bit

using SSH not on the standard port 22 but always use a custom port in the 50000 range for security reasons.

Wanted to enablie the Plesk Firewall (instead of using "homemade" iptables) but lost connectivity to SSH. Checked the preview of the Plesk Firewall and it wants to allow access on port 22, not the port we have specified in /etc/ssh/sshd_config

Can anyone confirm?

[am aware, can just leave the Plesk SSH Firewall setting and create my own specialised rule]
 
Last edited:
Hello Tom,

Plesk is NOT aware of your custom preset SSH port ...
Only you know that and it's you to allow that custom port in it's firewall ...

By default SSH port in the firewall is defined by 22 which is the cause of that behaviour ..

**If you don't define and allow your custom port, despite allowing SSH through the firewall, you will still NOT have access to SSH on your server.
 
Ahh, thanks for explanation. :)

Thought [had hoped] as the SSH port is only configured in that one config file, Plesk would grab it from there automatically instead of using a 'hard coded' default...
learned something new again :)

Cheers,
Tom
 
Back
Top