# Ignition Client will not launch, throws error

**URL:** <https://forum.inductiveautomation.com/t/ignition-client-will-not-launch-throws-error/37155>\
**Category:** Ignition\
**Created:** [July 28, 2020, 12:45pm UTC](https://forum.inductiveautomation.com/t/ignition-client-will-not-launch-throws-error/37155 "2020-07-28T12:45:59Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![franklepkowski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/franklepkowski/32/4808_2.png) [@franklepkowski](https://forum.inductiveautomation.com/u/franklepkowski)\
**Post date:** [July 28, 2020, 12:45pm UTC](https://forum.inductiveautomation.com/t/ignition-client-will-not-launch-throws-error/37155/1 "2020-07-28T12:45:59Z")

</div>

![Error](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/f/bf988a56fb9a0961e705f2d77bce6d7f0f8e31f8.png)

Guys,

Any ideas what this error means? Client will not launch. 8.0.13

Thanks,

Frank

---

<div class="post-metadata">

**Author:** ![code\_skin](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@code\_skin](https://forum.inductiveautomation.com/u/code_skin)\
**Post date:** [July 28, 2020, 12:52pm UTC](https://forum.inductiveautomation.com/t/ignition-client-will-not-launch-throws-error/37155/2 "2020-07-28T12:52:05Z")

</div>

If this is happening on a particular device and not others I’d start by clearing the local Ignition cache.  
Assuming you’re on a windows device you can paste the following into the explorer:  
**%userprofile%\.ignition\cache**  
Delete the contents inside.  
Relaunch client.

It’s something simple to try before staff can help you out.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [July 28, 2020, 1:08pm UTC](https://forum.inductiveautomation.com/t/ignition-client-will-not-launch-throws-error/37155/3 "2020-07-28T13:08:02Z")

</div>

I would also see if deleting (or moving, in case it needs to be moved back) the `~/.ignition/cache/resources/runtimes/11.0.6/lib/security/cacerts` file fixes this.

The runtime version in your path may differ.

---

<div class="post-metadata">

**Author:** ![franklepkowski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/franklepkowski/32/4808_2.png) [@franklepkowski](https://forum.inductiveautomation.com/u/franklepkowski)\
**Post date:** [July 28, 2020, 2:21pm UTC](https://forum.inductiveautomation.com/t/ignition-client-will-not-launch-throws-error/37155/4 "2020-07-28T14:21:58Z")

</div>

Hi guys,

Deleting the cache resolved the issue.

Thanks,

Frank

---

<div class="post-metadata">

**Author:** ![jharrell](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@jharrell](https://forum.inductiveautomation.com/u/jharrell)\
**Post date:** [February 22, 2021, 8:59pm UTC](https://forum.inductiveautomation.com/t/ignition-client-will-not-launch-throws-error/37155/5 "2021-02-22T20:59:32Z")

</div>

I just had the same issue with a client unable to connect with 8.1.1, and clearing the cache worked for this one as well. Thanks -Joe

---

<div class="post-metadata">

**Author:** ![1AngelG](https://avatars.discourse-cdn.com/v4/letter/1/dc4da7/32.png) [@1AngelG](https://forum.inductiveautomation.com/u/1AngelG)\
**Post date:** [October 11, 2021, 6:24pm UTC](https://forum.inductiveautomation.com/t/ignition-client-will-not-launch-throws-error/37155/6 "2021-10-11T18:24:54Z")

</div>

This did the trick. Thank you very much.

---

<div class="post-metadata">

**Author:** ![garrett.abe](https://avatars.discourse-cdn.com/v4/letter/g/e495f1/32.png) [@garrett.abe](https://forum.inductiveautomation.com/u/garrett.abe)\
**Post date:** [June 9, 2022, 6:07pm UTC](https://forum.inductiveautomation.com/t/ignition-client-will-not-launch-throws-error/37155/7 "2022-06-09T18:07:09Z")

</div>

Hello!

I have had this same issue on two Ignition Edge devices within the last month. Both times I was able to fix the issue by clearing the cache as stated in the previous comments. One of the devices was running Ignition 8.0.10 and the other was 8.0.16

Has anyone been able to identify a root cause for this issue?
