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

Question Moving to Plesk, LetsEncrypt Certificates

iansen

New Pleskian
Hello,
I'm moving a website to a new Plesk powered server.
I would like to make the move seamless.
I plan on moving the backend first and keep the database on the old server until all the traffic switches to the new IP.
But I have an issue/question with/about the LetsEncrypt Certificates.
How can I keep both servers running with valid certificates, for a day or two until the DNS changes propagate?
Does requesting a new certificate for my domain in Plesk invalidate the old certificates?
How can I just use the old certificates until I make the change? I
I've tried uploading the pem in the domain configuration panel ...but it's saying it's invalid (although it's working fine on the old server).
Am I missing something?

I'm new to Plesk, sorry if my questions sound stupid :).

Thanks in advance.
 
AFAIK, the old certificate will remain valid until its expiration date. So what you could do:
  1. Lower the TTL of your domain to a low value (like 300 seconds) and wait until the previous TTL (usually 86400) has expired
  2. Set up the website on the new server (without the valid certificate) and make sure everything is working
  3. Change your DNS and point it to the new server and make sure that your authoritative nameservers are up to date
  4. Install the Let's Encrypt certificate on the new server
  5. If all goes well then you'll have a valid certificate on the new server and then you can take your time migrating the rest
 
Back
Top