• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Plesk upgrade / Unable to connect to some Plesk ports

Lrnt

Lrnt

Basic Pleskian
Hi,

I get the following message when I try to upgrade to 18.0.60 :

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

The article specifies the ports which must be open, my (plesk) firewall is activated but all the authorizations for plesk or installation program are present there.

I tried by deactivating the firewall but I got the same message.

Should I pay attention to it or not because I have a option like "I confirm that I want to continue despite the problems detected." to click.

Thanks
 
Kaspar said:
Are there any related log entries in the Plesk log at the time you tried to update?
Click to expand...
I am still looking for Plesk error logs... /var/log/plesk/systemupdatestool.log is not human readable.
Is there anything in panel to see Plesk log ? I can't find it...
 
I disable IPV6 due to curl/crontab/dns propagation errors. Absolutely no problem since.
Can it be related to this? I am the only one who has this pre check error message?

Please note that I made previous micro upgrade with no problem.
It just happened now with v.18.0.60
 
@Kaspar I am such an idiot, sorry. Log file path is in the warning message I just posted here...

Here is the problem:
INFO: STEP 16: Checking the availability of Plesk Panel TCP ports...
INFO: Unable to connect to IP address 2001:41d0:403:38e8:: on Plesk Panel non-secure HTTP port 8880: Connection timed out
INFO: Unable to connect to IP address 2001:41d0:403:38e8:: 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.60_14244/examiners/plesk_preupgrade_checker.log for details. Find the full list of the required open ports at
INFO: Result: WARNING
Click to expand...
So it is related to IPV6 which I disabled as previsouly mentionned.
Is there anything I can do or should I continue the update despite the warning ?
 
Ok... Sorry for annoying you with this...

I am thinking that removing the IPV6 address from Plesk IPs* and reread IPs then updating will do the trick.
I will try tomorrow and keep you informed...

* I just disabled IPV6 but never removed the IP in Plesk IPs
 
Ok solved ! :cool:

If, like me, you need to disable IPV6, follow this article:
How to disable IPv6 addresses on a Plesk server? - Support Cases from Plesk Knowledge Base

Then, while upgrading, if you get another warning like "FTP service cannot be started by xinetd on Plesk server if IPv6 is disabled", follow this article:
https://support.plesk.com/hc/en-us/...by-xinetd-on-Plesk-server-if-IPv6-is-disabled

After that, Plesk will upgrade if no warning.

Thanks to @Kaspar for opening my eyes to the right logs to read
 
Good to read you've got it resolved, and thank you for sharing your solution. All credit for solving the issue belong to you. You've solved this by your self :)
 
Got the same error message today when upgrading to v18.0.62.

I did the same thing again by disabling IPv6 (Even though it was already disabled).

I then got the following error message: "[WARNING] IP address registered in Plesk is invalid or broken".

I followed the article https://www.plesk.com/kb/support/plesk-pre-upgrade-checker-shows-warning-ip-address-registered-in-plesk-is-invalid-or-broken/

Repairing did nothing but as I don't use IPv6 at all, I applied the second option, which is to completely delete the IPv6 address.

After this, I was able to update without problem.
 
Same error message again.
Delete IPV6 in Plesk as I don't use it (0 website on it) and already disabled in /etc/sysctl.conf

Then upgrade Plesk without any error.

I am repeating myself but just to let you that this problem exists.
 
You must log in or register to reply here.

Similar threads

Z
Issue Blocked ports 25-587
Replies
1
Views
395
zihniates
Z
R
Issue Unable to connect to FTP via
Replies
4
Views
779
kilowhisky65
K
M
Resolved Unable to export database. Error message: -- Connecting to localhost... mariadb-dump: Got error: 1045: "Access denied for user '<userx>'@'localhost'
Replies
1
Views
261
maredzki
M
J
Question Plesk Firewall is blocking requests even with configured rules
Replies
2
Views
1K
Johnny9977
J
GDuck24
Issue 18.0.59 (Update #2) failing to update to 18.0.60
Replies
5
Views
2K
VNick
V
Back
Top