# Site still missing the cert

**URL:** https://community.letsencrypt.org/t/site-still-missing-the-cert/112664
**Category:** Help
**Created:** [February 8, 2020, 1:24pm UTC](https://community.letsencrypt.org/t/site-still-missing-the-cert/112664 "2020-02-08T13:24:35Z")
**Posts on this page:** 1
**Showing post:** 15

<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 8, 2020, 11:09pm UTC](https://community.letsencrypt.org/t/site-still-missing-the-cert/112664/15 "2020-02-08T23:09:15Z")

</div>

> [@facildeanotar](#):
>
> how do you know that my nginx just serves the subdomain certificate?

It _did_ that, but now that you've got a certificate with both hostnames, there's no certificate issue any longer. Also, your HTTP site redirected all non-encrypted traffic to the `www` subdomain with HTTPS, so normally users wouldn't be bothered by a warning, as normally users would not end up to the HTTPS non-www hostname.

I tested the above with the command:

openssl s\_client -connect [slidepipe.com:443](http://slidepipe.com:443) -servername [slidepipe.com](http://slidepipe.com) | openssl x509 -noout -text

Which shows the contents of the certificate provided by the webserver for the hostname earlier in the command.

---

_[View the full topic](https://community.letsencrypt.org/t/site-still-missing-the-cert/112664)._