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

Firewall blocked Plesk (maybe?)

M

meister_li

Guest
Hi! I tryed to install a teamspeakserver on my Fedora Core 4 Rootserver with plesk. Since it wasn't reachable from the internet, I tryied forwarding the ports in the firewall, wich didn't work. So I activated the pre-entered config "accept all" but after doing this, Plesk wasn't reachable anymore (and the TS-Sever wasn't as well, while the webserver works properly). What did I wrong and how to fix that? (I have ssh-acces via putty to the server)
 
You must log in or register to reply here.

Similar threads

Z
Issue Firewall stopped working after update to Plesk Obsidian v18.0.77 on Debian 11.11
Replies
12
Views
4K
Kaspar
K
I
Resolved Preventing bot brute force probes against Postfix/SMTP
Replies
5
Views
980
iainh
I
L
Question Question before activating Plesk firewall
Replies
2
Views
2K
VanessaChuuy
VanessaChuuy
S
Issue Cant activate the plesk firewall
Replies
5
Views
5K
martinez.marcias@gmai
M
TimReeves
Issue Messages from a Plesk component appearing on root ssh console
Replies
9
Views
4K
TimReeves
TimReeves
Back
Top