• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Let's Encrypt Cert for https://subdm.mydomain.tld:8443

UweP

Regular Pleskian
Hi.

I've set up let's encrypt cert for plesk, and im using that cert to secure plesk, but still it says insecure in chrome? How can that be, it worked before! I renewed etc. nothing helps.

Thanks for any help!

Greetings, freaky.
 
Hi UweP,

did you consider to provide your complete URL, so that people willing to help you have something to start with the investigations together with you?
Or did you consider to post relevant log - entries from your "panel.log", where the Plesk Let's Encrypt extension logs its actions?

At the moment, we have only the choice to point you to the Plesk documentation or/and to the following Plesk KB - articles:

 
ok well, I just checked the panel.log tried to login with my new browser (switched to firefox-beta) and now suddenly its "secured" ... well, seems to be fixed for me. thank you! :)
 
Back
Top