Search results

You mean you want the same certificate installed on a domain and on its subdomains, am I correct? How it works now: you have to issue the wildcard certificate for the domain via LE extension the certificate will be assigned to the domain automatically after that you can manually assign the...

Nice ideas, thanks!

Thanks! Could you provide me with exact text of the warnings? To fix the issue we should repeat it :) You can use private message if there are sensitive data.

1. if you've got the certificate without using the Let's Encrypt Extension, the autorenewal feature won't work for those certificates, because we don't touch "foreign" certificates. But there is a trick - rename the certificate to "Lets Encrypt <old_name>" and the extension will treat the...

Hi. We've released the first version: Repair Kit - Plesk Extensions Please, participate in the survey, it will only takes 3-5 minutes: Repair Kit 1.0

The first version of the extension consists of two modules: Diagnose & Repair (is absent in the trailer) and Process List. Diagnose & Repair provides UI for "plesk repair" utility, Process List provides UI and some BL (the link between Plesk domain and the process) for "ps uax" utility. We...

Hi. Plesk doesn't provide such functionality. And, unfortunately, I don't think it's possible to get it done manually. The config for mailman is: <VirtualHost 10.52.52.133:7080 127.0.0.1:7080> DocumentRoot "/var/www/vhosts/default/htdocs" ServerName lists ServerAlias...

Hi. This feature is in the backlog. We thought it's easy, and we've started the implementation, but we've faced with a lot of small technical nuances that ruined the feature :( In other words, not in the nearest releases, sorry. Deep technical research is required here.

We’ve just released the new version of Let’s Encrypt Extension: Let's Encrypt - Plesk Extensions The main feature of the release is wildcard certificates autorenewal. Changelog: 2.7.0 (31 October 2018) Expired wildcard certificates can now be renewed automatically. Resolved a number of...

The extension is in testing stage now. I'll update this thread when it will be available :)

Hi @Gherardo. If the issue still exists, could you send me 'ps uaxwww | grep installer'?

@JohnBee thanx. What's your web-browser and platform (mac, win, lin)?

Hello. We’ve just released Advisor 1.4: Advisor - Plesk Extensions Changelog: 1.4.0 (24 October 2018) [+] Added the recommendation to use up-to-date WordPress and WordPress plugins. [+] Added the recommendation to use the Google PageSpeed Insights Pro extension. [+] Added the recommendation...

Yes, ETA is Fall (Autumn) 2018 :)

Released! Repair Kit - Plesk Extensions Notes: available for Plesk Onyx 17.8+ two modules included, both can be found in "Tools & Settings" page, "Assistance and Troubleshooting" section: Diagnose & Repair Process List

Hi @c0m. 1. I'd suggest using "Keep secured" option in your case. It works as you wish - if domain alias can't be secured, "Keep secured" option removes this problem alias from the CSR and issue the SSL certificate without this problem alias. This option can be set via Service Plan. Note...

Hi @camaran You're using Plesk UI, right? Did you see any errors when you issued the wildcard certificate? How do you check that there are no *.domainName in the certificate?

Hi @Michael Neikes. Sorry, don't sure I've understood your case correctly. Do you mean setting server mail certificate? If you mean server mail certificate - in MailEnable in that tab you see certificates as a list of Subject Names, in Plesk you see "user friendly" name of a certificate...

Hi. Regarding Juggernaut Firewall - good point, thanks.

Hi @Dennis Oppelt DigiCert Extension (former Symantec Extension) has been developed by Symantec. I agree that the form validation is too strong, but, I guess, it's required by CA validation policy. I'm also not so experienced with DigiCert CA, so, I'd suggest contacting DigiCert support...