Dukemaster
Regular Pleskian
Hi at all,
please, I don't want to see problems where is nothing unsual and everything alright.
But since the todays update of Lets encrypt extension, more the update few days ago since it's possible to create a certificate for the whole server PLESK, IPs, mail and default domains. This is amazing.
For this I had to create an extended certificate hardly by my own (Multi domain.com) one month ago.
Now PLESK + Lets Encrypt offer this great service ! ! !
I wonder about the fact that for the sub domain, which is also my servers hostname and points to servers default IPv4 and IPv6, 2 certificates are created. My hope and question is that they don't have side effects in successful running services like IP (network) and mainly Email.
For my hostname I created a subdomain. In the settings of the subdomain I created a Letsencrypt certificate like for all other domains/subdomains too.
But now by the new feature creating serverwide certificates in other repository I realized that they have the same domain name (in this case subdomain name) server.arox.eu.
For the process itself it sounds logic, but there appear questions for the correct functionality of e.g. securing emails.
In other words which certificate shall I use for the subdomain settings server.arox.eu in the subscription area?
Better like usual the subdomain special certificate, or perhaps to have a allround setup to take the server repository certificate?
From my stomach feeling I would take two different certificates, each for the depending service, means 1 for (subdomain webhosting) and 1 for securing Plesk server/hostname/mail/IP.
- Additional question is: How to find out for which service the Plesk certificates are used? (Tools & settings - Security - SSL/TLS Certificates)
Greets
please, I don't want to see problems where is nothing unsual and everything alright.
But since the todays update of Lets encrypt extension, more the update few days ago since it's possible to create a certificate for the whole server PLESK, IPs, mail and default domains. This is amazing.
For this I had to create an extended certificate hardly by my own (Multi domain.com) one month ago.
Now PLESK + Lets Encrypt offer this great service ! ! !
I wonder about the fact that for the sub domain, which is also my servers hostname and points to servers default IPv4 and IPv6, 2 certificates are created. My hope and question is that they don't have side effects in successful running services like IP (network) and mainly Email.
For my hostname I created a subdomain. In the settings of the subdomain I created a Letsencrypt certificate like for all other domains/subdomains too.
But now by the new feature creating serverwide certificates in other repository I realized that they have the same domain name (in this case subdomain name) server.arox.eu.
For the process itself it sounds logic, but there appear questions for the correct functionality of e.g. securing emails.
In other words which certificate shall I use for the subdomain settings server.arox.eu in the subscription area?
Better like usual the subdomain special certificate, or perhaps to have a allround setup to take the server repository certificate?
From my stomach feeling I would take two different certificates, each for the depending service, means 1 for (subdomain webhosting) and 1 for securing Plesk server/hostname/mail/IP.
- Additional question is: How to find out for which service the Plesk certificates are used? (Tools & settings - Security - SSL/TLS Certificates)
Greets
Last edited: