# Installed Let's Encrypt SSL not showing HTTPS **URL:** \ **Category:** Help\ **Created:** [February 5, 2019, 12:51pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306 "2019-02-05T12:51:33Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![emchagara](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/emchagara/32/29673_2.png) [@emchagara](https://community.letsencrypt.org/u/emchagara)\ **Post date:** [February 5, 2019, 12:51pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/1 "2019-02-05T12:51:33Z")
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [https://crt.sh/?q=example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help. My domain is: www.mca.ac.ug I ran this command: I used instructions from this video [https://www.youtube.com/watch?v=WqCk9dVLoPw](https://www.youtube.com/watch?v=WqCk9dVLoPw) It produced this output: Successfully installed certificate but website still shows insecure on many browsers My web server is (include version): Apache. Shared webhosting The operating system my web server runs on is (include version): NGINX My hosting provider, if applicable, is: eUKhost LTD I can login to a root shell on my machine (yes or no, or I don’t know): NO I’m using a control panel to manage my site (no, or provide the name and version of the control panel): cPanel 76.0.18 The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you’re using Certbot): Not Sure ---
**Author:** ![sltux](https://avatars.discourse-cdn.com/v4/letter/s/ac8455/32.png) [@sltux](https://community.letsencrypt.org/u/sltux)\ **Post date:** [February 5, 2019, 1:04pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/2 "2019-02-05T13:04:12Z")
did you install ssl chain ? fullchain,pem ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [February 5, 2019, 1:16pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/3 "2019-02-05T13:16:14Z")
There is a cert mismatch: [https://www.ssllabs.com/ssltest/analyze.html?d=www.mca.ac.ug](https://www.ssllabs.com/ssltest/analyze.html?d=www.mca.ac.ug) [one site is using another sites’ cert] ---
**Author:** ![sltux](https://avatars.discourse-cdn.com/v4/letter/s/ac8455/32.png) [@sltux](https://community.letsencrypt.org/u/sltux)\ **Post date:** [February 5, 2019, 1:41pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/4 "2019-02-05T13:41:23Z")
> [@emchagara](#): > > www.mca.ac.ug you can try -d \*.mca.ac.ug -d mca.ac.ug ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [February 5, 2019, 1:44pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/5 "2019-02-05T13:44:33Z")
> [@sltux](#): > > you can try -d \*.mca.ac.ug -d mca.ac.ug Three things wrong with that: 1. Always use quotes around asterisks; so: `-d "*.mca.ac.ug" -d mca.ac.ug` 2. The mismatched cert is from a completely different domain ("[milima.org](http://milima.org)"), so a wildcard cert won't change anything. 3. Wildcard certs would require changing the authentication method to DNS. ---
**Author:** ![emchagara](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/emchagara/32/29673_2.png) [@emchagara](https://community.letsencrypt.org/u/emchagara)\ **Post date:** [February 5, 2019, 1:44pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/6 "2019-02-05T13:44:43Z")
I followed every instruction on that video so I can’t tell what went wrong. I also need to be honest, I am quite novice when it comes to SSL installations. Is there a site which offers step by step instructions on how to install SSL by Lets Encrypt for Wordpress website. Please note that I have no access to root but I have access to cPanel. Thanks again. ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [February 5, 2019, 1:47pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/7 "2019-02-05T13:47:25Z")
I’m not familiar with cPanel. But I do see that your sites works without the “www”: [https://www.ssllabs.com/ssltest/analyze.html?d=mca.ac.ug&latest](https://www.ssllabs.com/ssltest/analyze.html?d=mca.ac.ug&latest) So, perhaps, you just need to include the www as an alias and get a new cert that contains both names: “mca.ac.ug” & “www.mca.ac.ug” ---
**Author:** ![sltux](https://avatars.discourse-cdn.com/v4/letter/s/ac8455/32.png) [@sltux](https://community.letsencrypt.org/u/sltux)\ **Post date:** [February 5, 2019, 1:48pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/8 "2019-02-05T13:48:42Z")
No need to put “” on wildcard domain . I didn’t see milima,org . just checked www.mca.ac.a=ug. 😃 ---
**Author:** ![emchagara](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/emchagara/32/29673_2.png) [@emchagara](https://community.letsencrypt.org/u/emchagara)\ **Post date:** [February 5, 2019, 1:52pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/9 "2019-02-05T13:52:06Z")
Is there a site which would give me step by step instructions so that I don’t repeat the same mistakes. Also, how do I deal with the stray domain [milima.org](http://milima.org)? ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [February 5, 2019, 1:54pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/10 "2019-02-05T13:54:06Z")
> [@sltux](#): > > No need to put “” on wildcard domain Please don't say that. Even if it works on your system that will NOT work on all systems. ---
**Author:** ![sltux](https://avatars.discourse-cdn.com/v4/letter/s/ac8455/32.png) [@sltux](https://community.letsencrypt.org/u/sltux)\ **Post date:** [February 5, 2019, 1:55pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/11 "2019-02-05T13:55:12Z")
Hm . that is correct . ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [February 5, 2019, 1:57pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/12 "2019-02-05T13:57:27Z")
> [@emchagara](#): > > Is there a site which would give me step by step instructions so that I don’t repeat the same mistakes. The Internet is full of information, so I guess yes there is. But I don't use cPanel and don't know of any particular site. > [@emchagara](#): > > How do I deal with the stray domain [milima.org](http://milima.org)? That is not something you need to "fix". It is a side effect of the web server looking for a name that it can't serve. So it serves the first/default site that matches the type of request (https). You "fix" it by providing cPanel a way to know where "www.mca.ac.ug" is. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [March 7, 2019, 1:57pm UTC](https://community.letsencrypt.org/t/installed-lets-encrypt-ssl-not-showing-https/85306/13 "2019-03-07T13:57:39Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.