Resolved Server unreachable, 24 hours after reboot

[DaarGaJeDan]

Hi Guys,

My plesk server suddently unreachable on all ports. The server is up to date.
It happened after a licence renewal. Looks like it happends 24 hours after a reboot.

What i tried:

• # plesk repair all -v
  After restart everything runs but no website or mail can be reached.
  After a new reboot i the websites and mail came online.....
• 24 hours after this last report server is unreachable aswel, except for the vpn consol

I found in the kern.log Around the time off the blocking.
Jan 21 02:34:12 s2 named[720]: no longer listening on <Server IP>#53
Jan 21 02:35:01 s2 CRON[129292]: (root) CMD (/opt/psa/bin/sw-engine-pleskrun /opt/psa/admin/plib/DailyMaintainance/task-script.php StoreOutgoingMessagesStatistics >/dev/null 2>&1)

Does any one have a suggestion?


My server:
OS:
Ubuntu 20.04.3 LTS

Product:
Plesk Obsidian, Version 18.0.41, last updated on Jan 18, 2022 11:13 PM

 

[eliamarsura]

You could try to uninstall and reinstall fail2ban and plesk firewall.

And you can try to check ti iptables rules:

iptables -nL

You may look something like this:

Chain INPUT (policy ACCEPT)
target prot opt source destination
f2b-plesk-postfix tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 25,465,587

Chain FORWARD (policy DROP)
target prot opt source destination
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain f2b-plesk-postfix (1 references)
target prot opt source destination
RETURN all -- 0.0.0.0/0 0.0.0.0/0

If you see, for example:

Chain INPUT (policy DROP)

this could be your problem

 

[DaarGaJeDan]

HI,
I think it is fixed. It had to do something with the DHCP release of the service provider of my VPS.

After setting a static ip, and we aint relying on the DHCP the symptoms disapeared.

Thanks for the help!