Certificate issued but https not working


#1

Hey, I am using Lets Encrypt SSL for my domain in windows server 2012. In the browser showing certificate issued but https not working. Can you please help us on this?


#2

Hi @pennyful,

What’s your domain? How did you install the certificate? How do you know the certificate was issued, and what error do you get in the browser?


#3

Hi Schoen,

My domain name: www.pennyful.in
I have follwled this link to install https://www.youtube.com/watch?v=Z3jd8NOOY2o
attached the screenshot.

Please help us on this.


#4

You forgot to include www.pennyful.in on your certificate. You only included pennyful.in.

I’m don’t use Windows so I’m not sure exactly how it’s done with the method shown in the video, but it looks like you need to select both bindings (for www.pennyful.in and pennyful.in) for the IIS website when issuing the certificate.


#5

Thnaks for your reply! Will check.


#6

I am facing the same issue… certificate issued properly but sometimes https works sometimes it doesn’t…
I have updated all URLs to https but still, it is not working.
https://www.pickpurifier.com/


#7

@princemoga, what’s your domain name? What errors do you see when it doesn’t work?


#8

Hi - I’m having a similar issue. I installed Free Wordpress SSL on cherichristian.com, dyllis.net, and a few other sites but it is not showing up. This was installed via the Bluehost control panel. When I log back in and try to install it on these domains, it says You have already purchased a certificate for this domain.


#9

When I say its not showing up I mean the site isn’t showing as secure in most browsers. Thank you for any feedback.


#10

Hi @cgl102770,

Ultimately, this problem isn’t related to @pennyful’s earlier problem because you’re seeing a different kind of browser error. In @pennyful’s case the problem was with the certificate itself, but in your case the problem is with the site content.

What you’re seeing is a mixed content error, where some of the site resources such as images, scripts, or stylesheets are hard-coded in your HTML source to be loaded from HTTP URLs instead of HTTPS URLs. For example, if you have <img src="http://example.com/picture.jpg" /> in your page source, it will be marked as insecure by browsers.

A real example from dyllis.net is that you have

<img src="http://dyllis.net/wp-content/uploads/2015/10/logo_blank.png" alt="Dyllis" width="288" />

which instead needs to be

<img src="https://dyllis.net/wp-content/uploads/2015/10/logo_blank.png" alt="Dyllis" width="288" />

I recommend using https://www.whynopadlock.com/ to scan your sites for a list of what’s causing this problem.


#11

That makes good sense, thank you for the reply!


#12

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.