# NodeJS scripts timeout

**URL:** <https://forum.dfinity.org/t/nodejs-scripts-timeout/18490>\
**Category:** Developers\
**Created:** [February 15, 2023, 5:17am UTC](https://forum.dfinity.org/t/nodejs-scripts-timeout/18490 "2023-02-15T05:17:45Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![rckprtr](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/rckprtr/32/809_2.png) [@rckprtr](https://forum.dfinity.org/u/rckprtr)\
**Post date:** [February 17, 2023, 8:34pm UTC](https://forum.dfinity.org/t/nodejs-scripts-timeout/18490/21 "2023-02-17T20:34:17Z")

</div>

```auto
"@dfinity/agent": "^0.15.3",
    "@dfinity/candid": "^0.15.3",
    "@dfinity/identity": "^0.15.3",
    "@dfinity/identity-secp256k1": "^0.15.3",
    "@dfinity/principal": "^0.15.3",

```

---

<div class="post-metadata">

**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\
**Post date:** [February 17, 2023, 8:41pm UTC](https://forum.dfinity.org/t/nodejs-scripts-timeout/18490/22 "2023-02-17T20:41:12Z")

</div>

Aaaaah agent-js version! Gotcha, thanks for the feedback. Same for me.  
I have now forwarded all error messages of the thread to the team.

---

<div class="post-metadata">

**Author:** ![mbeekman](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/mbeekman/32/2675_2.png) [@mbeekman](https://forum.dfinity.org/u/mbeekman)\
**Post date:** [February 17, 2023, 8:55pm UTC](https://forum.dfinity.org/t/nodejs-scripts-timeout/18490/23 "2023-02-17T20:55:31Z")

</div>

So after some testing here, we have been able to be recreate the intermittent connection with node18 + dfinity v0.15.3

but, node16 with @dfinity v0.14.1 works fine and is stable … We only started to experience any of the time outs when we updated to 0.15.3 of @dinfity npm and node18 … and can basically reproduce this over and over … hope it helps …

---

<div class="post-metadata">

**Author:** ![peterparker](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@peterparker](https://forum.dfinity.org/u/peterparker)\
**Post date:** [March 11, 2023, 1:36pm UTC](https://forum.dfinity.org/t/nodejs-scripts-timeout/18490/24 "2023-03-11T13:36:37Z")

</div>

UPDATE: We just debugged this issue with @raymondk as it turned out I was finally able to replicate it consistently today (Saturday, funday 😉) . While it isn’t clear why yet, we figured out the issue was linked with few particular machines when accessed through IPv6. We will continue to investigate but, we are on good track.

---

<div class="post-metadata">

**Author:** ![raymondk](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/raymondk/32/6174_2.png) [@raymondk](https://forum.dfinity.org/u/raymondk)\
**Post date:** [March 13, 2023, 5:42pm UTC](https://forum.dfinity.org/t/nodejs-scripts-timeout/18490/25 "2023-03-13T17:42:26Z")

</div>

Hi folks - an update here.  
We were able to track this down to a firewall rule blocking public ipv6 traffic to 2 of the boundary node VMs.  
It was fine when you were using the VPN but if you happened to have ipv6 at home and resolve DNS to to one of those boundary nodes you would see a timeout.

Thanks everyone for reporting the issue and special thanks to @peterparker for helping debug 😉

---

<div class="post-metadata">

**Author:** ![rckprtr](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/rckprtr/32/809_2.png) [@rckprtr](https://forum.dfinity.org/u/rckprtr)\
**Post date:** [March 13, 2023, 7:42pm UTC](https://forum.dfinity.org/t/nodejs-scripts-timeout/18490/26 "2023-03-13T19:42:32Z")

</div>

I can confirm that its working on my end

[Previous page](https://forum.dfinity.org/t/nodejs-scripts-timeout/18490.md?page=1)