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

Server Reboot

W

WarBirD

Guest
Server Reboot + PLESK Firewall ?

Hi,

i have a problem with what i have to admit, i can´t fix. I have PLESK 7.5 running on my rented Debian Root Server. The PSA was running and I had just the ports blocked and open that I needed. 2 days ago, i decided, because i had some strange problem with my webserver, to make a reboot.

But after the reboot the Server didn´t came back. So after hours of wondering why, i wrote a support ticket to my serverhoster and he wrote me that the Server had in fact rebooted but was blocked for any port other than 2.

NMAP:

Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2006-09-30
15:16 CEST

Interesting ports on xxx.server4you.de (xx.xx.xx.xx):

(The 1661 ports scanned but not shown below are in state: closed)

PORT STATE SERVICE

80/tcp open http

443/tcp open https



Nmap finished: 1 IP address (1 host up) scanned in 2.106 seconds

How the hell could this happen after a reboot ? I am not so the linux & server expert, i must admit, this is not solvable for me, I just dont know what the problem is. I checked the PSA Settings on the console, the Ports were exactly the same that was set from me, so those ports couldn´t be closed but they are.

Someone suggested that maybe something isn´t started correctly anymore when the Server boots but i find the psa-firewall Files in the /etc/rc?.d folder, so it should have been started.

What can be the problem ? I am thankful for any help.

WarBirD
 
I am not very familiar with Debian, but it sounds like the operating system has firewall rules that are loading after PSA and overriding the PSA rules.

I would poke around in your sysinit scripts. I know on Red Hat distributions you can do "/sbin/chkconfig --list iptables" to see if the OS is loading firewall rules.
 
Back
Top