![]() ![]() ![]() Spot on and this is the Obsidian section of the forum There's a separate Onyx (incl 17.8.11) section. Upgrading to Obsidian is much less work and easier However, it does (certainly did for us) solve the e-mail problem in 17.8.11. By default, new Plesk installations come with pre-installed Let's Encrypt extension and if the server's hostname is correct, Plesk secures itself automatically. You might get a No SNI warning on on domains, but only on the 2nd certificate that's shown when testing on etc but that's slightly irrelevent as the 1st certificate has only one domain name on it. If you read all of THIS old thread, right to the end, first of all before doing anything, it might explain things about this option for you too. THIS (acme.sh) which is excellent & works regardless of Plesk. Mailboxes, Websites, databases and Letsencrypt. There are currently just the default preinstalled plesk-panel default certificate under Tools->SSL Certs and the not working letsencrypt cert unter domain -> exampledomain. I migrated only 2 domains from an older Starto V-Server with Ubuntu 14.04 and Plesk 12.5 to test the migration. The letsencrypt module fails to secure the (only) domain and the plesk panel on a fresh installed plesk system with a restored domain from backup (by Odin). This still works, even if all of your DNS is outside of Plesk, as ours was & still is) plus, you still cannot use the Plesk Let's Encrypt Extension to generate the Let's Encrypt Multi-Domain Wildcard Certificate. I ordered a new Strato V-Server with Ubtuntu 16.04 LTS and Plesk Onyx 17.8 (Web Pro edition). The downsides are all those already mentioned, but those do include manual certifcate renewals only (including all the DNS verification posts & checks - two of these on each domain, because they are all wildcard status. We know it works, because that's how we ran our own Plesk setup back when we were using 17.8.11. Plesk by default takes the email from the owner of the domain to secure. In this Multi-Domain Wildcard Certificate, every domain has the wildcard option and one of those domains, must be the domian where you're hosting Plesk itself from. In the drop-down list, select Lets Encrypt certificate (server pool) and click OK. Now, to secure a Plesk mail server, click Change next to Certificate for securing mail. This certificate will be auto-renewed every 90 days. The option is to generate one Let's Encrypt Multi-Domain Wildcard Certificate as well as all the normal certificates. At this stage, an SSL certificate from Let’s Encrypt is generated and set to secure Plesk on port 8443 automatically. Choose the certificate assigned to subdomain and click OK. Find the option Certificate for securing Plesk and click on Change button right to it. it takes a LOT of setup, a LOT of patience, it's never going to be perfect and the law of diminishing returns applies dependent on how many domains you're hosting. On Windows: C:> plesk bin extension -exec letsencrypt cli.php -secure-plesk -m -w 'pleskdirdefaulthtdocs' -d . Specifically this comment helped me understand what to do: After assigning a Let’s Encrypt certificate to a subdomain just go to Tools & Settings > SSL/TLS Certificates. ![]() However, there is still an option for 17.8.11 but. Click to expand.Spot on and this is the Obsidian section of the forum There's a separate Onyx (incl 17.8.11) section. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |