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

Plesk Update Catastrophe

J

Janson0

Guest
Hi Everyone,

I just upgraded my plesk installation from v9.0.1 to v9.3 via the Plesk Panel Upgrade Icon. The report on the upgrade said the upgrade went perfectly, but I am now not able to access the panel. It says that it cannot find the server, and yet when i go to the IP address the Plesk Header is shown.

At first, several of my domains were down. I went in and updated the permissions of those folders, because apparently on the upgrade Plesk reduced the permissions to some of the virtual hosts. All my domains are up, consequently, but I cannot access the Plesk Console.

You can view my server's issue here:
https://65.182.110.102:8443

I think it might be a permissions issue with the plesk console itself?

Please help!!
Michael Anderson
 
Seems that reason of this problem is problem with resolving:

$ host 65.182.110.102
Host 102.110.182.65.in-addr.arpa not found: 3(NXDOMAIN)

$ host mdanderson.brinkster.net
Host mdanderson.brinkster.net not found: 3(NXDOMAIN)
 
Well,

If you just navigate to that IP address, you get the plesk default domain page.

Also, before the update the address was resolving... so I am not sure what happened to make that not resolve? I am assuming it is something that the Plesk Update changed settings wise.
 
Back
Top