# Pritunl Client v1.3.3463.71 - Unhandled rejection message

**URL:** <https://forum.pritunl.com/t/pritunl-client-v1-3-3463-71-unhandled-rejection-message/835>\
**Category:** Pritunl VPN\
**Tags:** pritunl-client\
**Created:** [March 7, 2023, 7:06pm UTC](https://forum.pritunl.com/t/pritunl-client-v1-3-3463-71-unhandled-rejection-message/835 "2023-03-07T19:06:35Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![meerkataries](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/m/9e8a1a/32.png) [@meerkataries](https://forum.pritunl.com/u/meerkataries)\
**Post date:** [March 7, 2023, 7:06pm UTC](https://forum.pritunl.com/t/pritunl-client-v1-3-3463-71-unhandled-rejection-message/835/1 "2023-03-07T19:06:35Z")

</div>

Getting this error message when I open the client. It goes away after a few seconds, and it does not appear to affect the connection itself. VPN connects just fine.

Uninstalling the client does not solve the warning.

 ![pritunl client error](https://forum-static.pritunl.com/original/1X/4f2315c2d8348820062c83475a6d02916a2fab4d.png)

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [March 7, 2023, 7:47pm UTC](https://forum.pritunl.com/t/pritunl-client-v1-3-3463-71-unhandled-rejection-message/835/2 "2023-03-07T19:47:57Z")

</div>

Open the Console in the Developer Tools from the top right menu to utilize the source map for the error.

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [March 7, 2023, 8:45pm UTC](https://forum.pritunl.com/t/pritunl-client-v1-3-3463-71-unhandled-rejection-message/835/3 "2023-03-07T20:45:07Z")

</div>

This is most likely an error from loading the system profiles before the service is ready. It should get reloaded again without effecting the client.

---

<div class="post-metadata">

**Author:** ![meerkataries](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/m/9e8a1a/32.png) [@meerkataries](https://forum.pritunl.com/u/meerkataries)\
**Post date:** [March 7, 2023, 10:36pm UTC](https://forum.pritunl.com/t/pritunl-client-v1-3-3463-71-unhandled-rejection-message/835/4 "2023-03-07T22:36:41Z")

</div>

No profiles, this was after deploying on a brand-new system.  
If it helps, I’m able to replicate with other Windows 10 Pro 64bit systems.

 ![image](https://forum-static.pritunl.com/original/1X/3729c4a6b8c5cd86df227b9e6ee534b5dd6270e4.png)

 ![image](https://forum-static.pritunl.com/original/1X/54b9a8b33e60649a8d23bff259221b0740500d12.png)

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [March 7, 2023, 11:11pm UTC](https://forum.pritunl.com/t/pritunl-client-v1-3-3463-71-unhandled-rejection-message/835/5 "2023-03-07T23:11:55Z")

</div>

Check the service logs in the top right menu under view logs. If it’s not working open the file at `C:\ProgramData\Pritunl\pritunl-client.log`.

---

<div class="post-metadata">

**Author:** ![meerkataries](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/m/9e8a1a/32.png) [@meerkataries](https://forum.pritunl.com/u/meerkataries)\
**Post date:** [March 7, 2023, 11:23pm UTC](https://forum.pritunl.com/t/pritunl-client-v1-3-3463-71-unhandled-rejection-message/835/6 "2023-03-07T23:23:53Z")

</div>

Just to be clear, it’s not actually causing issues to connect.  
That’s working fine, just an ugly warning to see if you need to open the client.

Here is that I see under logs:

 ![image](https://forum-static.pritunl.com/original/1X/01eab63d0b978f4974f38acb76705a01b1c053cb.png)

Client Logs have more to say:

[2023-3-7 17:21:15][ERROR] Main: Unhandled rejection message=t is not iterable stack=TypeError: t is not iterable  
at ko.\_sync (file:///C:/Program%20Files%20(x86)/Pritunl/resources/app.asar/dist/static/app.988cce.js:73:552586)  
at ko.\_callback (file:///C:/Program%20Files%20(x86)/Pritunl/resources/app.asar/dist/static/app.988cce.js:73:553504)  
at t.\_invokeCallback (file:///C:/Program%20Files%20(x86)/Pritunl/resources/app.asar/dist/static/app.988cce.js:29:12464)  
at t.dispatch (file:///C:/Program%20Files%20(x86)/Pritunl/resources/app.asar/dist/static/app.988cce.js:29:12286)  
at file:///C:/Program%20Files%20(x86)/Pritunl/resources/app.asar/dist/static/app.988cce.js:73:556065  
at process.processTicksAndRejections (node:internal/process/task\_queues:96:5)  
UnknownError: Main: Unhandled rejection message=t is not iterable stack=TypeError: t is not iterable  
at ko.\_sync (file:///C:/Program%20Files%20(x86)/Pritunl/resources/app.asar/dist/static/app.988cce.js:73:552586)  
at ko.\_callback (file:///C:/Program%20Files%20(x86)/Pritunl/resources/app.asar/dist/static/app.988cce.js:73:553504)  
at t.\_invokeCallback (file:///C:/Program%20Files%20(x86)/Pritunl/resources/app.asar/dist/static/app.988cce.js:29:12464)  
at t.dispatch (file:///C:/Program%20Files%20(x86)/Pritunl/resources/app.asar/dist/static/app.988cce.js:29:12286)  
at file:///C:/Program%20Files%20(x86)/Pritunl/resources/app.asar/dist/static/app.988cce.js:73:556065  
at process.processTicksAndRejections (node:internal/process/task\_queues:96:5)  
at window.onunhandledrejection (file:///C:/Program%20Files%20(x86)/Pritunl/resources/app.asar/dist/static/app.988cce.js:73:609322)

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [March 8, 2023, 12:12am UTC](https://forum.pritunl.com/t/pritunl-client-v1-3-3463-71-unhandled-rejection-message/835/7 "2023-03-08T00:12:37Z")

</div>

This was caused by a race condition. The init was not correctly waiting for the configuration file to load, it appears to take slightly longer on Windows 10 causing the profile load request to come before the configuration finishes loading.

It won’t happen if there are already non-system profiles imported as those profiles are read from disk before requesting system profiles. That is enough delay to keep the sequence correct. To fix the issue close the error message and import profiles then restart the app. This will be fixed in an update later today.
