# Self-signed certificate with litium-storefront proxy

**URL:** <https://forum.litium.com/t/self-signed-certificate-with-litium-storefront-proxy/3506>\
**Category:** Questions\
**Created:** [August 5, 2025, 2:30pm UTC](https://forum.litium.com/t/self-signed-certificate-with-litium-storefront-proxy/3506 "2025-08-05T14:30:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![adam.clettborn](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.litium.com/adam.clettborn/32/956_2.png) [@adam.clettborn](https://forum.litium.com/u/adam.clettborn)\
**Post date:** [August 5, 2025, 2:30pm UTC](https://forum.litium.com/t/self-signed-certificate-with-litium-storefront-proxy/3506/1 "2025-08-05T14:30:00Z")

</div>

I’m using a self-signed dev-cert using dotnet dev-certs, and it is working properly with any \*.localtest.me site using that certificate. However, when running the proxy, it always returns an invalid certificate.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/litium/original/1X/ae387a5a9345f3c1dda04f05880855e4014243d4.png)

To bypass the “insecure connection” page in chrome I can type “thisisunsafe”, which is kind of annoying.

How can I fix this properly?

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex030/uploads/litium/original/1X/12eddac3b8b661de1db86af10ac8151b571e6fb9.png) [@system](https://forum.litium.com/u/system)\
**Post date:** [September 2, 2025, 2:30pm UTC](https://forum.litium.com/t/self-signed-certificate-with-litium-storefront-proxy/3506/2 "2025-09-02T14:30:07Z")

</div>

Closed on September 2, 2025, 2:30pm UTC

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