I don’t own the site but i seed this when i visit on this site.
This issue was because some of the website’s resources was loaded in http, not https.
Most of the times this can be solved by updating Nginx/Apache rule to force https.
To be clear, Let’s Encrypt only issues certificates. That’s just a small part of the correct implementation of HTTPS (TLS). A very great part of it, is server configuration of the website. And that isn’t something Let’s Encrypt can ultimately control.
Similarly, someone selling tires for a car can’t directly ensure that the car’s engine has enough oil, even though both are necessary to the car’s proper operation.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.