Question Plesk update

[mariodieck]

Hello, I was trying to update from version 18.0.75 to version 18.0.76. However, I'm getting the following warning:

Plesk pre-upgrade check
WARNING: Unable to connect to some Plesk ports. Please see /root/parallels/pool/PSA_18.0.76_18469/examiners/plesk_preupgrade_checker.log for details. Find the full list of the required open ports at https://support.plesk.com/hc/articles/12377821243159


In the plesk_preupgrade_checker.log I find the following

INFO: STEP 16: Checking the availability of Plesk Panel TCP ports...
INFO: Unable to connect to IP address fdba:17c8:6c94::1011 on Plesk Panel non-secure HTTP port 8880: Connection timed out
INFO: Unable to connect to IP address fdba:17c8:6c94::1011 on Plesk Panel secure HTTPS port 8443: Connection timed out
WARNING: Unable to connect to some Plesk ports. Please see /root/parallels/pool/PSA_18.0.76_18469/examiners/plesk_preupgrade_checker.log for details. Find the full list of required open ports at https://support.plesk.com/hc/articles/12377821243159

After checking ports (8880, 8443) using `iptables -nL | grep 8443` and `iptables -nL | grep 8880`, the following output is displayed:

astra7082:~# iptables -nL | grep 8443
f2b-plesk-login 17 -- 0.0.0.0/0 0.0.0.0/0 multiport dports 443,8880,8443
f2b-plesk-login 6 -- 0.0.0.0/0 0.0.0.0/0 multiport dports 443,8880,8443
astra7082:~# iptables -nL | grep 8880
f2b-plesk-login 17 -- 0.0.0.0/0 0.0.0.0/0 multiport dports 443,8880,8443
f2b-plesk-login 6 -- 0.0.0.0/0 0.0.0.0/0 multiport dports 443,8880,8443

What could be the problem?

 

[Sebahat.hadzhi]

Hi, @mariodieck . Could you please try:

nmap -sT -6 fdba:17c8:6c94::1011 -p 8443,8880

If you are able to access Plesk and perform the upgrade, the warning message could generally be safely ignored.

 

[mariodieck]

nmap -sT -6 fdba:17c8:6c94::1011 -p 8443,8880 outputs the following:

astra7082:~# nmap -sT -6 fdba:17c8:6c94::1011 -p 8443,8880
-bash: nmap: command not found.

 

[mariodieck]

If you are able to access Plesk and perform the upgrade, the warning message could generally be safely ignored.

I'm just afraid that something will go wrong.