• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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