Question Plesk pre-upgrade check - Checking Components Before Updating

[weareimpulse]

Server operating system version

Ubuntu 24.04.4 LTS

Plesk version and microupdate number

Plesk Obsidian 18.0.78 Update #4 Web Host Edition

hi, my automatic updates for the PLESK version have stopped. When i went to update them manually, i'm getting this message:

Plesk pre-upgrade check

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

Any advice, please? thanks!

 

[Sebahat.hadzhi]

Hi, @weareimpulse . Do you have custom ports configured for Plesk? Also, is the server in question behind a NAT? If possible, please attach the log file from the message root/parallels/pool/PSA_18.0.79_19264/examiners/plesk_preupgrade_checker.log for further review.

 

[weareimpulse]

hi, its not behind a NAT. Heres the log file. Seems to be Nº14 its got the error.

INFO: Installed Plesk version/build: 18.0.78 Ubuntu 24.04 1800260617.20...

INFO: STEP 0: Detect system configuration...
INFO: OS: Ubuntu 24.04.4 LTS \n \l
INFO: Arch: x86_64

INFO: Validating the database password...
INFO: Result: OK

INFO: Pre-Upgrade analyzer version: 18.0.79.0...

INFO: STEP 1: Checking for main IP address...
INFO: Result: OK

INFO: STEP 2: Checking existence of Plesk user "root" for MariaDB/MySQL database servers...
INFO: Result: OK

INFO: STEP 3: Checking proftpd settings...
INFO: Result: OK

INFO: STEP 4: Checking the 'Interval' parameter in the sw-collectd configuration file...
INFO: Result: OK

INFO: STEP 5: Checking Apache status...
INFO: Result: OK

INFO: STEP 6: Checking Panel files for the immutable bit attribute...
INFO: Result: OK

INFO: STEP 7: Checking the possibility to change the permissions of files in the DUMP_D directory...
INFO: Result: OK

INFO: STEP 8: Checking consistency of the IP addresses list in the Panel database...
INFO: Result: OK

INFO: STEP 9: Checking for custom web server configuration templates...
INFO: Result: OK

INFO: STEP 10: Checking for domains with mixed case names...
INFO: Result: OK

INFO: STEP 11: Checking symbolic link /usr/local/psa on /opt/psa...
INFO: Result: OK

INFO: STEP 12: Detecting if encrypted passwords are used...
INFO: Result: OK

INFO: STEP 13: Checking table "servers" in database "mysql"...
INFO: The administrator's password for the default MariaDB/MySQL server is encrypted.
INFO: Result: OK

INFO: STEP 14: Checking the availability of Plesk Panel TCP ports...
INFO: Unable to connect to IP address 217.154.34.159 on Plesk Panel secure HTTPS port 8443: Connection refused
WARNING: Unable to connect to some Plesk ports. Please see /root/parallels/pool/PSA_18.0.79_19264/examiners/plesk_preupgrade_checker.log for details. Find the full list of the required open ports at https://support.plesk.com/hc/articles/12377821243159
INFO: Result: WARNING

INFO: STEP 15: Checking if Atmail is used by domains...
INFO: Result: OK

INFO: STEP 16: Checking for Protected Directory Users with duplicates in login field....

INFO: STEP 17: Checking "domains" table with duplicates in guid field....

INFO: STEP 18: Checking "clients" table with duplicates in guid field....

INFO: STEP 19: Checking if any rules are configured in the Firewall extension...

 

[Sebahat.hadzhi]

It looks like port 8443 is closed.

nmap -sT -4 217.154.34.159 -p 8443,8880

Could you please double-check the configuration of the firewall(s)? Also, are you able to normally access Plesk on ports 8443 and 8880? Additionally, does the update go through or is it interrupted?

 

[weareimpulse]

So I can only access Plesk via 8443 and not 8880. However, I've run the update, and it did complete fine, so I guess it's all good