• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Plesk firewall ignores rules??

J

jaimet

Guest
Hi,

I've installed the plesk firewall module, and set a custom rule to open the port 43.

I go to Firewall, add custom rule, and set;

Outgoing
Allow,
43 port TCP, 43port UDP
from any machine,

So i suppose that tis will open outgoing server requests to port 43..

Next i store the rule, and activate the firewall setup. But the server is still ignoring my telnet requests:

telnet whois.crsnic.net 43

gets no response.
 
Please go to Linux console and type iptables-save.
If you will see custom rule in whole index, it means that you have problem with your iptables (or you have add this rule in wrong place).

In mostly cases i think PSK dont reload your rules, so you will not see it in the index.
Do then this step: /etc/init.d/psa-firewall restart (in RHEL OSes).

To developers: PSK really have problem with firewall reload.

Regards,
Alex
 
Damn!!

I discovered that my isp has it's own firewall outside the server, and they block the port 43, so if i must pay to open it!

I think it had nothing to do with plesk... arggg
 
Back
Top