Title: no https Last modified: January 29, 2017 --- # no https * Resolved [papaworx](https://wordpress.org/support/users/papaworx/) * (@papaworx) * [9 years, 2 months ago](https://wordpress.org/support/topic/no-https-2/) * I run WP with the CommentPress plugin. I have a free “Let’s Encrypt SSL” certificate installed. Yet, any attempt at connecting to my WP site via https reverts to http. The apparent culprit is “mixed content”. I have examined user accessible templates, style sheets and images. None contains an explicit http call. One of the test plugins claimed it was due to a “reverse proxy”, so I threw out DreamFlare. In Chrome, I get : “NET::ERR_CERT_COMMON_NAME_INVALID”. Is the problem in the server, the proxy, the SSL certificate, WordPress, CommentPress, in the content, or somewhere else? Viewing 5 replies - 1 through 5 (of 5 total) * Thread Starter [papaworx](https://wordpress.org/support/users/papaworx/) * (@papaworx) * [9 years, 2 months ago](https://wordpress.org/support/topic/no-https-2/#post-8712709) * In the meantime I found that all links in the as well as media appear with absolute http: uri’s. * Plugin Author [webaware](https://wordpress.org/support/users/webaware/) * (@webaware) * [9 years, 2 months ago](https://wordpress.org/support/topic/no-https-2/#post-8713601) * G’day papaworx, * It sounds like your website certificate doesn’t match your website’s domain name. Can you share the URL to your site so that we can inspect it? * cheers, Ross * Thread Starter [papaworx](https://wordpress.org/support/users/papaworx/) * (@papaworx) * [9 years, 2 months ago](https://wordpress.org/support/topic/no-https-2/#post-8719727) * [http://Stuehlingen.online/Book](http://Stuehlingen.online/Book) * Thanks * Plugin Author [webaware](https://wordpress.org/support/users/webaware/) * (@webaware) * [9 years, 2 months ago](https://wordpress.org/support/topic/no-https-2/#post-8723150) * I just took a look, and it all looks good to me in Chrome and Firefox — did you find and fix your problem? * cheers, Ross * Thread Starter [papaworx](https://wordpress.org/support/users/papaworx/) * (@papaworx) * [9 years, 2 months ago](https://wordpress.org/support/topic/no-https-2/#post-8724410) * Yes, the provider had made a mistake with the certificate and fixed it after the fourth attempt yesterday afternoon. Thanks for your help. Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘no https’ is closed to new replies. * ![](https://ps.w.org/ssl-insecure-content-fixer/assets/icon-256x256.png?rev=2590634) * [SSL Insecure Content Fixer](https://wordpress.org/plugins/ssl-insecure-content-fixer/) * [Frequently Asked Questions](https://wordpress.org/plugins/ssl-insecure-content-fixer/#faq) * [Support Threads](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/) * [Active Topics](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/unresolved/) * [Reviews](https://wordpress.org/support/plugin/ssl-insecure-content-fixer/reviews/) ## Tags * [SSL problems](https://wordpress.org/support/topic-tag/ssl-problems/) * 5 replies * 2 participants * Last reply from: [papaworx](https://wordpress.org/support/users/papaworx/) * Last activity: [9 years, 2 months ago](https://wordpress.org/support/topic/no-https-2/#post-8724410) * Status: resolved