> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/kb/media-players/lg-webos-displays-and-self-signed-certificates.md).

# LG webOS Displays and self-signed certificates

If you have an on-premise CMS that uses a self-signed SSL certificate, you may see that your connection is being rejected. This is because the webOS Display will not accept self-signed certificates.

To resolve this you will need to import the public portion of the self-signed certificate in use by your CMS into the screen so that the certificate becomes trusted.

{% hint style="info" %}
C and D series models only support importing self-signed certificates to be trusted. Later models (for example E series) support the import of a root CA certificate into the Trust Store which means you can use certificates signed by a central CA for your organisation.
{% endhint %}

To import your certificate you need to have it in X.509 (PEM) format, and you’ll need a USB stick to load it on to.

On your USB stick, create a folder and a subfolder named LG\_MONITOR/CERTIFICATE and put the CRT file into that subfolder to ensure that the webOS device can “see” it. 

1. Connect the USB stick to your webOS Display
2. From the TV menu, go to **SI Server Settings**
3. Then goto **Self-Signed Certificate** and select your certificate to import from the USB stick

If at all possible, use publicly recognised SSL certificate authorities which webOS already trusts to sign your certificates, as it removes the need to configure any trust on the TV.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xibosignage.com/kb/media-players/lg-webos-displays-and-self-signed-certificates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.