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

udgrade from 10 to 10.1 fails

W

wildwilla

New Pleskian
udgrade from 10 to 10.1 fails - SOLVED

Hiya

I am trying to upgrade from 10 t o10.1 but the install fails with teh following error (text file attached) and the plesk user frontend is now not avalible, but the install cp on port 8447 is still available.

Any ideas?

Ww
 

Attachments

  • parallels-installation-log.txt
    8.9 KB · Views: 7
Last edited:
so i managed to get the cp working again by doing "/etc/init.d/psa restart".

Will make sure everything is working fine and then I wil readdress the upgrade again.

Ww
 
You must log in or register to reply here.

Similar threads

M
Issue Database Connection Refused 10 mins after Deploy
Replies
1
Views
438
scsa20
scsa20
S
Issue Plesk 18.0.64 Restore failing
Replies
1
Views
738
Sebahat.hadzhi
Sebahat.hadzhi
Linulex
Issue roundcube upgrade fails from 18.0.63 to 18.0.64 when mariadb 10.11.9 is installed
Replies
4
Views
928
Linulex
Linulex
T
Resolved Grafana fails: Option '[alerting].enabled' cannot be true. Legacy Alerting is removed. It is no longer deployed, enhanced, or supported.
Replies
12
Views
3K
Paulo_o
P
Lexz
Resolved 'CP User Login Attempt via API Failed' ('Login Name': '<invalid>' => '')
Replies
3
Views
1K
Lexz
Lexz
Back
Top