# DevKinsta 2.8.0 SSL Certificate Not Valid

**URL:** https://community.kinsta.com/t/devkinsta-2-8-0-ssl-certificate-not-valid/1852
**Category:** Application Support
**Created:** [November 4, 2022, 5:24pm UTC](https://community.kinsta.com/t/devkinsta-2-8-0-ssl-certificate-not-valid/1852 "2022-11-04T17:24:52Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![sharpspring](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/sharpspring/32/3507_2.png) [@sharpspring](https://community.kinsta.com/u/sharpspring)
#### Post date: [November 7, 2022, 6:12pm UTC](https://community.kinsta.com/t/devkinsta-2-8-0-ssl-certificate-not-valid/1852/8 "2022-11-07T18:12:46Z")

</div>

Kevin,

I’m on Big Sur 11.6 and did not change versions before the issue started.

I’ve also found a workaround for Firefox

If you go to Firefox \> Preferences \> Privacy & Security you can add the server as an exception

 ![Screen Shot 2022-11-07 at 1.09.10 PM](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/5/5ef106cf54470f49c312d3d2b068d8201d20a9cb.png)

Clicking View Certificates as seen in screenshot will allow you add the full domain name (including port value if different) as an exception which so far allows me to bypass the warning in browser.

---

_[View the full topic](https://community.kinsta.com/t/devkinsta-2-8-0-ssl-certificate-not-valid/1852)._