• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Migration Error, default certifcate

P

priora

Guest
Hello, iam getting always the error that the default certificate allready exist.

Plesk help tells me "Rename the default certificate on the one of the servers and perform migration once again."

But I have no fecking clou how where I can do that?! Can anybody help me please?

Thank you
 
Priora, what Plesk version do you use?
For example, for Plesk 10.4.4 you can use next way:
login to Control Panel as admin -> Tools & Settings -> SSL Certificates -> default certificate.
 
You must log in or register to reply here.

Similar threads

Azurel
Issue MariaDB 11.8.8: STRICT_TRANS_TABLES suddenly enabled after reboot AlmaLinux 9.7 → 9.8
Replies
2
Views
1K
Azurel
Azurel
D
Forwarded to devs SSL It! / Let's Encrypt DNS-01 challenge remains permanently "Pending" – TXT records created successfully but challenge is never confirmed
Replies
3
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
N
Issue Issues with migration from web host to web admin
Replies
2
Views
4K
nelteren
N
kristobal1969
Resolved Error messages with let's Encrypt when 1 serveur for main domain and another serveur for subdomain or mails
Replies
12
Views
6K
NataliaA
N
Azurel
Not used PHP versions removed, but Plesk reports missing versions
Replies
4
Views
3K
Azurel
Azurel
Back
Top