# SSL update failed

**URL:** <https://community.kinsta.com/t/ssl-update-failed/1893>\
**Category:** Bug Reports\
**Created:** [November 22, 2022, 10:28am UTC](https://community.kinsta.com/t/ssl-update-failed/1893 "2022-11-22T10:28:07Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dezpfab](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/dezpfab/32/1566_2.png) [@dezpfab](https://community.kinsta.com/u/dezpfab)\
**Post date:** [November 22, 2022, 10:28am UTC](https://community.kinsta.com/t/ssl-update-failed/1893/1 "2022-11-22T10:28:07Z")

</div>

**Q: Date/Time this occurred (Provide your time zone also)**  
**A:11/22/2022**

**Q: DevKinsta Version**  
**A:2.8.0**

**Q: OS Version**  
**A:Mac OS Monterey 12.6**

**Q: Docker Desktop Version**  
**A:4.14.1**

**Q: Were any error codes or messages observed? If so, what were they?**  
**A:NET::ERR\_CERT\_AUTHORITY\_INVALID (on Chrome) and "SSL update failed (on DevKinsta when toggling HTTPS**

**Q: Detailed Description of the Problem**  
**A: After importing a website, when I try to access, I end up on the following error message (NET::ERR\_CERT\_AUTHORITY\_INVALID). I’ve tried to toggle back HTTPS on DevKinsta but I get the following error message (SSL updated failed). Pretty annoying for developpement as I have to bypass Chrome error message every time**

Issue is pretty similar to this one : [DevKinsta 2.8.0 SSL Certificate Not Valid - #3 by dinu](https://community.kinsta.com/t/devkinsta-2-8-0-ssl-certificate-not-valid/1852/3)

---

<div class="post-metadata">

**Author:** ![Kevin](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/kevin/32/808_2.png) [@Kevin](https://community.kinsta.com/u/Kevin)\
**Post date:** [November 22, 2022, 5:18pm UTC](https://community.kinsta.com/t/ssl-update-failed/1893/2 "2022-11-22T17:18:20Z")

</div>

Hi @dezpfab, thanks for reaching out. The Chrome SSL issue is still being investigated by our developers (and other local application devs) but we understand it better now.

I’m not 100% sure if the “SSL update failed” is purely because of this, though. Just to be sure, can you please try to toggle it again then private message your main.log file to me? I’ll be sure to share it with our developers.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/9/9448ab63872a4f6099f1370706644f21d61eb514.png)

---

<div class="post-metadata">

**Author:** ![krisroadruck](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/krisroadruck/32/1536_2.png) [@krisroadruck](https://community.kinsta.com/u/krisroadruck)\
**Post date:** [November 23, 2022, 7:01pm UTC](https://community.kinsta.com/t/ssl-update-failed/1893/3 "2022-11-23T19:01:20Z")

</div>

devkinsta is adding the cert to the login chain, but it needs to be in the system chain for chrome to like it

you can copy/paste it from login to system and make chrome happy (might require a chrome restart)

---

<div class="post-metadata">

**Author:** ![dinu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/dinu/32/1579_2.png) [@dinu](https://community.kinsta.com/u/dinu)\
**Post date:** [November 29, 2022, 1:42pm UTC](https://community.kinsta.com/t/ssl-update-failed/1893/4 "2022-11-29T13:42:16Z")

</div>

@Kevin [^This](https://community.kinsta.com/t/ssl-update-failed/1893/3) fixed my issue from the “[DevKinsta 2.8.0 SSL Certificate Not Valid](https://community.kinsta.com/t/devkinsta-2-8-0-ssl-certificate-not-valid/1852)” thread.  
Thanks, @krisroadruck!

---

<div class="post-metadata">

**Author:** ![rseitzberg](https://avatars.discourse-cdn.com/v4/letter/r/90ced4/32.png) [@rseitzberg](https://community.kinsta.com/u/rseitzberg)\
**Post date:** [November 29, 2022, 7:18pm UTC](https://community.kinsta.com/t/ssl-update-failed/1893/5 "2022-11-29T19:18:01Z")

</div>

This fixed my problem too! I am on Mac OS Ventura 13.0.1 and when I copied and pasted the certificate from “login” in keychain access to “system” then restarted chrome, chrome didn’t create an ssl error message anymore.

---

<div class="post-metadata">

**Author:** ![krisroadruck](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/krisroadruck/32/1536_2.png) [@krisroadruck](https://community.kinsta.com/u/krisroadruck)\
**Post date:** [November 29, 2022, 9:06pm UTC](https://community.kinsta.com/t/ssl-update-failed/1893/6 "2022-11-29T21:06:36Z")

</div>

Glad I was able to help. Bit worried between this and the firefox folder SSL bug on linux I’m gonna end up being known as the devKinsta SSL fix guy lol

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/8/80f8c4e56fecc02327a0964e6bf63a716483529f.png) [@system](https://community.kinsta.com/u/system)\
**Post date:** [January 31, 2023, 2:57am UTC](https://community.kinsta.com/t/ssl-update-failed/1893/7 "2023-01-31T02:57:08Z")

</div>

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