• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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