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

Issue Can't open/close Firewall ports

Beinemann

New Pleskian
This seems a little bit odd but although Plesk tells me that Plesk Firewall is working fine it doesn't seem to work. Online port scanner / Nmap see things different, too.
I tried to open Port 9987 udp for incoming data for a Teamspeak server (after the Server software wasn't working correctly though it told me that it would/everything is running fine, Plesk says) and I see the applied rule in the Firewall rules list, but neither TS is working nor port scanner say the certain port is opened.
Modifying other rules won't work as well (even the scenario allowing all incoming traffic).
I am working with Plesk Obsidian 18.0.27 (Update 1 installed). Anyone has an idea what could cause this?
 
If the port is clearly open in Plesk and it is still not open from the outside, look elsewhere. Many providers operate firewalls before their servers that cannot be configured from within Plesk but from within their server control panels. For example, OVH is using such firewalls. You need to open the port there, too.
 
Back
Top