# New Member Requesting Help No Padlock

**URL:** <https://community.letsencrypt.org/t/new-member-requesting-help-no-padlock/145026>\
**Category:** Help\
**Created:** [February 10, 2021, 6:50pm UTC](https://community.letsencrypt.org/t/new-member-requesting-help-no-padlock/145026 "2021-02-10T18:50:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sfwservers](https://avatars.discourse-cdn.com/v4/letter/s/a9adbd/32.png) [@sfwservers](https://community.letsencrypt.org/u/sfwservers)\
**Post date:** [February 10, 2021, 6:50pm UTC](https://community.letsencrypt.org/t/new-member-requesting-help-no-padlock/145026/1 "2021-02-10T18:50:33Z")

</div>

I have installed letsencrypt successfully and ran a check on [Test Results: sickfreakingweirdos.com - Why No Padlock?](https://www.whynopadlock.com/results/5d0c261e-b97e-4ff4-a8cf-ddf4a7d76577) and everything seems to be okay, however, going to [https://sickfreakingweirdos.com](https://sickfreakingweirdos.com) still shows site as insecure.

I have gone thru wordpress to make sure that https:// is being used.

Appreciate any help you can render. Thank you.

Best regards,  
Ferdinand

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. [crt.sh | 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: [sickfreakingweirdos.com](http://sickfreakingweirdos.com)

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot):

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [February 10, 2021, 7:13pm UTC](https://community.letsencrypt.org/t/new-member-requesting-help-no-padlock/145026/2 "2021-02-10T19:13:28Z")

</div>

The certificate is only valid for `sickfreakingweirdos.com`, but you have a redirect from `https://sickfreakingweirdos.com` to `https://www.sickfreakingweirdos.com` in place.

---

<div class="post-metadata">

**Author:** ![sfwservers](https://avatars.discourse-cdn.com/v4/letter/s/a9adbd/32.png) [@sfwservers](https://community.letsencrypt.org/u/sfwservers)\
**Post date:** [February 11, 2021, 8:22am UTC](https://community.letsencrypt.org/t/new-member-requesting-help-no-padlock/145026/3 "2021-02-11T08:22:47Z")

</div>

hmmm any idea where this might be?  
thank you Osiris.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [February 11, 2021, 8:24am UTC](https://community.letsencrypt.org/t/new-member-requesting-help-no-padlock/145026/4 "2021-02-11T08:24:31Z")

</div>

No, because you didn't specify how you got the cert and with what client. So I can't guess how that happened and thus no idea how to fix it. Please answer all the questions of the initial questionnaire to the best of your knowledge.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [March 13, 2021, 8:24am UTC](https://community.letsencrypt.org/t/new-member-requesting-help-no-padlock/145026/5 "2021-03-13T08:24:45Z")

</div>

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