The let's encrypt extension is great, except... it doesn't work for me: It doesn't add domain aliases. I have domains like "typing-error.de", "typing-eror.de", "typing-errror.de", "typing-error.com" etc. (you get the idea). As-is, only the primary domain is added to the certificate.306 votes
Let’s Encrypt 2.0.0 extension with this feature is now available!
We would love to hear your feedback on our forum at http://talk.plesk.com. We’d like to thank everyone who commented on this request and provided invaluable feedback. Thanks!
We now have the ability to issue wildcard certificates via GUI, but it would be handy to issue the wildcard certificates via CLI as well22 votes
Available since SSL It! 1.4.0 (4 June 2020): https://ext.plesk.com/packages/3c4117f6-c05c-4d3b-9173-60f10096a9c4-sslit#!
Add ability to disable Wildcard certificate option in Let's Encrypt18 votes
Available since Let’s Encrypt Extension 2.8.3.
“2.8.3 (24 October 2019)
[+] Introduced the allow-wildcard-certificates option (true by default) under the ext-letsencrypt section in the panel.ini file. If set to false, the option hides the feature of issuing wildcard SSL/TLS certificates in the interfaces of the Let’s Encrypt and SSL It! extensions.
Note: For the same purpose, users could earlier use the acme-protocol-version setting with the acme-v01 value. If you have this configuration, we recommend that you start using allow-wildcard-certificates set to false because the ACMEv1 protocol will soon reach end of life."
Let's support this please. Add support for ASP.NET Core 2 for Plesk Onyx17 votes
I’m glad to inform you that this functionality was added since Plesk Onyx 17.8 release :) Plesk detects if ASP.NET Core 2 is installed or you can install it as a component via Plesk Installer (Tools&Settings → Updates & Upgrades → Add/Remove Components). Then deploy your ASP.NET Core application to the website document root.
Plesk Onyx Release Notice: https://docs.plesk.com/release-notes/onyx/change-log/
As Let's Encrypt keeps on telling me to renew my certificates and plesk tells me that it automatically rene s 30 days before expiration it would be handy to actually SEE the expiration date on the let's encrypt or on the certificate pages.11 votes
The feature is available in Advisor extension (Plesk Onyx 17.8) as “Security > Secure Websites With SSL/TLS Certificates” recommendation.
Let's support this please. aspnetcore 2.1 has got the official version, Add support for ASP.NET Core 2.1 for Plesk Onyx7 votes
Added support for ASP.NET Core 2.2.2 (Plesk for Windows) – https://docs.plesk.com/release-notes/onyx/change-log/#contents-179-preview12
Please take back MagicSpam as an extension in Plesk!1 vote
Unfortunately, not everything depends on us here. There are questions to MagicSpam side, vendor of this extension. The current situation with this you can monitor in this thread https://talk.plesk.com/threads/magicspam-extension-missing-in-extension-catalog-but-installed.348668/
Right now, you cannot set the git deploy-to directory until after the repository is setup and deployed the first time. After you "fix" it, it deploys again on the new path, but does not clean up the wrong deployment it did during setup.
I use a "/data/web/htdocs" path for all my customers, and it is painful to reconfigure git deployment for each of them. A default setting would be very nice.1 vote
Thank you for your input!
Could you please why you cannot change deploy-to directory via click “to /httpdocs/ directory”
(see right side on screenshot https://docs.plesk.com/en-US/onyx/administrator-guide/website-management/git-support/using-remote-git-hosting.75848/#o76294)?
Upd: Thank you for confirmation. We are closing the request as completed.
- Don't see your idea?