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

12.5 Upgrade Help

ae9803

New Pleskian
Hi All,
I am not sure where to start, I upgraded to 12.5 this morning and it completely broke my server. First, I am hosting two domains, so initially after it was complete both website were going to the Apache Centos default page, after running /usr/local/psa/bin/repair --web. I was able to clear that issue and the pages were loading correctly. Now, I cant access plesk @ ipaddress:8443. Anyone know where I can start?

Thanks,
Jake
 
Hi ae9803,

well, you could start to read: [IMPORTANT]: READ THIS FIRST TO FIND QUICK SOLUTION FOR THE EXISTING ISSUE/QUESTION

If the mentioned boostrapper repair didn't already helped you, to solve your issues, please have a closer look at the "repair" - utility with the command:

/usr/local/psa/bin/repair --help

Please keep in mind that errors are always logged, so investigations of your error - logs might point directly to the issue/problem. As mentioned in the above sticky thread, you find all sorts of error - logs, configuration file locations and standard commands at:



If you experience issues with the Plesk Control Panel, the first start is always to restart the service:

/etc/init.d/psa restart

This command is as well mentioned in the above KB - article and you will find as well the location of depending error - logs and configurations files there.
 
Hi ae9803,

well, you could start to read: [IMPORTANT]: READ THIS FIRST TO FIND QUICK SOLUTION FOR THE EXISTING ISSUE/QUESTION

If the mentioned boostrapper repair didn't already helped you, to solve your issues, please have a closer look at the "repair" - utility with the command:

/usr/local/psa/bin/repair --help

Please keep in mind that errors are always logged, so investigations of your error - logs might point directly to the issue/problem. As mentioned in the above sticky thread, you find all sorts of error - logs, configuration file locations and standard commands at:



If you experience issues with the Plesk Control Panel, the first start is always to restart the service:

/etc/init.d/psa restart

This command is as well mentioned in the above KB - article and you will find as well the location of depending error - logs and configurations files there.
Thanks for your reply!
 
Back
Top