# SSL certificate not trusted

**URL:** <https://forum.webostv.developer.lge.com/t/ssl-certificate-not-trusted/27444>\
**Category:** Web App Development\
**Created:** [July 30, 2025, 4:59am UTC](https://forum.webostv.developer.lge.com/t/ssl-certificate-not-trusted/27444 "2025-07-30T04:59:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![user1196](https://avatars.discourse-cdn.com/v4/letter/u/b77776/32.png) [@user1196](https://forum.webostv.developer.lge.com/u/user1196)\
**Post date:** [July 30, 2025, 4:59am UTC](https://forum.webostv.developer.lge.com/t/ssl-certificate-not-trusted/27444/1 "2025-07-30T04:59:23Z")

</div>

We are facing an issue on WebOS TVs where certain SSL certificates are not trusted.

For example: Accessing [https://media.axprod.net/](https://media.axprod.net/) results in the following error:

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/webostv/original/1X/652c77e14d71e4ba59ad7d776ab09316fcac1bfc.jpeg)

It affects model years 2016-2019 and 2022. I was only able to resolve it on 2023 through a software update. The certificate has enabled TLS 1.2 which should be supported on all platforms: [https://webostv.developer.lge.com/develop/specifications/tls](https://webostv.developer.lge.com/develop/specifications/tls)

I’m guessing it is caused by the Sectigo Root Certificates not being trusted by the platform.

Is this something that could be fixed?  
Thank you!

---

<div class="post-metadata">

**Author:** ![narae0.kim](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@narae0.kim](https://forum.webostv.developer.lge.com/u/narae0.kim)\
**Post date:** [July 30, 2025, 5:43am UTC](https://forum.webostv.developer.lge.com/t/ssl-certificate-not-trusted/27444/2 "2025-07-30T05:43:41Z")

</div>

Each webOS version has a list of trusted root certificates, and modification of this list is not allowed. If the root of your certificate does not exist in the list of trusted root certificates of the TV, you cannot use it. Sorry for not being helpful.

---

<div class="post-metadata">

**Author:** ![user1196](https://avatars.discourse-cdn.com/v4/letter/u/b77776/32.png) [@user1196](https://forum.webostv.developer.lge.com/u/user1196)\
**Post date:** [July 31, 2025, 7:27am UTC](https://forum.webostv.developer.lge.com/t/ssl-certificate-not-trusted/27444/3 "2025-07-31T07:27:07Z")

</div>

Thanks for your reply! Does that mean that it is also not possible to modify it through a software update? I’m just wondering, since this particular root CA is generally trusted by other major operating systems.

---

<div class="post-metadata">

**Author:** ![narae0.kim](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@narae0.kim](https://forum.webostv.developer.lge.com/u/narae0.kim)\
**Post date:** [July 31, 2025, 8:04am UTC](https://forum.webostv.developer.lge.com/t/ssl-certificate-not-trusted/27444/4 "2025-07-31T08:04:58Z")

</div>

Of course, the list can be updated with TV SW updates. However, it is not updated on request, and there’s no way to know when and which certificates will be added.

---

<div class="post-metadata">

**Author:** ![user1196](https://avatars.discourse-cdn.com/v4/letter/u/b77776/32.png) [@user1196](https://forum.webostv.developer.lge.com/u/user1196)\
**Post date:** [August 4, 2025, 4:37am UTC](https://forum.webostv.developer.lge.com/t/ssl-certificate-not-trusted/27444/5 "2025-08-04T04:37:31Z")

</div>

I see, thank you for the information!