• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Resolved Let's Encrypt Certificate invalid? failed to load resource: net::err_cert_common_name_invalid

ukeller66

New Pleskian
10 days ago I installed a new Server and move my one of my Domains https://www.optiliga.de to this installation. I saved this via plesk with a 'Let's Encrypt' certificate.
All works fine.
Yesterday I looked to the domain and see, it is broken. In console log I find the message "failed to load resource: net::err_cert_common_name_invalid". I checked all and cant finde the failure.
Has anyone an idea, where to seek?
 

Attachments

  • pic-1.JPG
    pic-1.JPG
    60.1 KB · Views: 2
No, not really. After I looking around a little bit, making some experiments with missing TXT-Records, I found the solution.

All CSS, JS, images and so on was loaded with 'https://www.optiliga.de/{the file}'. However, the name of the certificate is correct 'optiliga.de'. After I change the prefix to "'https://optiliga.de'" all works fine.

The question only is, whats the reason, that the old (wrong) version works before (At least some days)?
Anyway, never touch a running system.

Thanks for your support.
 
Last edited:
Back
Top