• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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 let's encrypt for AWS route53 DNS domain

S

Seba

Basic Pleskian
Hi all,

I have 2 hosted zone for 2 domains that are setup with AWS route 53 and each zone setup the domain to point to 2 server, each server contain a clone of these domains, till here everything is OK.

How can I use let's encrypt to secure those domains? can I simply use let's encrypt in both servers and secure each domain independently? and then 60 days after the certificate issue Plesk will renew the certificate?
 
You must log in or register to reply here.

Similar threads

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
M
Question Let's encrypt certificate emails do not contain certificate details
Replies
2
Views
4K
MHC_1
M
K
Resolved Plesk Obsidian – Let’s Encrypt certificate does not include domain aliases in SAN
Replies
7
Views
6K
kicoes
K
G
Issue Issue with duplicate SSL Certificate
Replies
9
Views
7K
Gerardo Fernandez
G
D
Question How to determine renewal period for ACME SSL?
Replies
3
Views
3K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top