# Production config demo server certificate warning

**URL:** <https://hub.mender.io/t/production-config-demo-server-certificate-warning/4739>\
**Category:** Yocto Project\
**Created:** [March 10, 2022, 1:52pm UTC](https://hub.mender.io/t/production-config-demo-server-certificate-warning/4739 "2022-03-10T13:52:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![B-Stefan](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/b-stefan/32/1473_2.png) [@B-Stefan](https://hub.mender.io/u/B-Stefan)\
**Post date:** [March 10, 2022, 1:52pm UTC](https://hub.mender.io/t/production-config-demo-server-certificate-warning/4739/1 "2022-03-10T13:52:39Z")

</div>

I have a question regarding the server certificate:

According to the [documentation](https://docs.mender.io/system-updates-yocto-project/build-for-production#preparing-the-server-certificates-on-the-client) there is no need for a manual server certificate if the certificate is signed by a know CA.

```auto
Including the server certificate on the client is only necessary if the certificate is not signed by a known Certificate Authority (CA) for example, if the certificate is self-signed. If signed by a known CA, the remainder of this section is not necessary.

```

According to my research, the certificate of the hosted version of mender is signed by a known CA.

But I still see the warning during the Yocto build and assume that I can ignore that warning.

Is that correct?

```auto
You are building with the default server certificate, which is not intended for production use

```

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [March 11, 2022, 1:41pm UTC](https://hub.mender.io/t/production-config-demo-server-certificate-warning/4739/2 "2022-03-11T13:41:28Z")

</div>

Hi @B-Stefan,

unfortunately that is not accurate. The message indicates that the demo certificated for a hosted Mender instance is in place, which is absolutely undesirable for production. As this note comes from the [meta-mender-demo](https://github.com/mendersoftware/meta-mender/blob/master/meta-mender-demo/recipes-mender/mender-server-certificate/mender-server-certificate.bbappend) layer, the correct solution is to remove that layer from the build setup altogether.

The message can and should be improved, though.

Greetz,  
Josef