# Certificate is not valid

**URL:** <https://community.letsencrypt.org/t/certificate-is-not-valid/203924>\
**Category:** Help\
**Created:** [August 22, 2023, 2:25pm UTC](https://community.letsencrypt.org/t/certificate-is-not-valid/203924 "2023-08-22T14:25:19Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![gfesj\_cgpbrasil](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@gfesj\_cgpbrasil](https://community.letsencrypt.org/u/gfesj_cgpbrasil)\
**Post date:** [August 22, 2023, 2:25pm UTC](https://community.letsencrypt.org/t/certificate-is-not-valid/203924/1 "2023-08-22T14:25:19Z")

</div>

I run a certbot

My domain is: [demo.wellcast-roi.com](http://demo.wellcast-roi.com)

I tried to access [https://demo.wellcast-roi.com](https://demo.wellcast-roi.com), but it shows me that certificate is not valid.

![Screenshot 2023-08-22 at 11.05.18](https://global.discourse-cdn.com/letsencrypt/original/3X/1/3/13389a4bb352188312c09aa14a1d93cdb81eed20.png)

I run at APACHE server at Centos 7.

How can we fix this?

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [August 22, 2023, 2:29pm UTC](https://community.letsencrypt.org/t/certificate-is-not-valid/203924/2 "2023-08-22T14:29:15Z")

</div>

You are using a certificate from the Let's Encrypt Staging system. It is great you used that to test but you must get a production certificate for actual use. See your cert details here:

> **[SSL Checker](https://decoder.link/sslchecker/demo.wellcast-roi.com/443)**
>
> Verify that your SSL certificate is installed correctly, identify installation issues if any.

How did you obtain the certificate? Please answer as much as you can from the form you were shown

===========================

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:

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:** ![gfesj\_cgpbrasil](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@gfesj\_cgpbrasil](https://community.letsencrypt.org/u/gfesj_cgpbrasil)\
**Post date:** [August 22, 2023, 2:43pm UTC](https://community.letsencrypt.org/t/certificate-is-not-valid/203924/3 "2023-08-22T14:43:16Z")

</div>

Thanks, here it is...

I ran this command: certbot certonly -a manual -d [demo.wellcast-roi.com](http://demo.wellcast-roi.com) --preferred-challenges dns --staging

OUTPUT I do not have here, but we can get certificates.

My Web server is: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips

My server is running: CentOS Linux release 7.9.2009 (Core)

My hosting provider, if applicable, is GCP

I can login to a root shell on my machine

The version of my client is certbot 1.11.0

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [August 22, 2023, 2:45pm UTC](https://community.letsencrypt.org/t/certificate-is-not-valid/203924/4 "2023-08-22T14:45:36Z")

</div>

> [@gfesj\_cgpbrasil](#):
>
> certbot certonly -a manual -d [demo.wellcast-roi.com](http://demo.wellcast-roi.com) --preferred-challenges dns **--staging**

Re-run the command without --staging to get a production cert

---

<div class="post-metadata">

**Author:** ![gfesj\_cgpbrasil](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@gfesj\_cgpbrasil](https://community.letsencrypt.org/u/gfesj_cgpbrasil)\
**Post date:** [August 22, 2023, 4:14pm UTC](https://community.letsencrypt.org/t/certificate-is-not-valid/203924/5 "2023-08-22T16:14:15Z")

</div>

Thanks for your help. It is work!

---

<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:** [September 21, 2023, 4:14pm UTC](https://community.letsencrypt.org/t/certificate-is-not-valid/203924/6 "2023-09-21T16:14:19Z")

</div>

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