# Node-red-contrib-speedtest config error

**URL:** <https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358>\
**Category:** General\
**Created:** [23 June 2023 03:24 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358 "2023-06-23T03:24:54Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![k5map](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/k5map/32/47681_2.png) [@k5map](https://discourse.nodered.org/u/k5map)\
**Post date:** [23 June 2023 03:24 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/1 "2023-06-23T03:24:54Z")

</div>

I've been using this node for almost a year without any issues until today... for some reason I'm now getting the error:

Error: Configuration - Could not retrieve or read configuration (ConfigurationError)

Has anyone experienced this issue? If so, how do I go about fixing it?

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [23 June 2023 09:04 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/2 "2023-06-23T09:04:53Z")

</div>

It looks like you have already opened a [GitHub issue](https://github.com/steffenmllr/node-red-contrib-speedtest/issues/27) which is what I would have suggested.

---

<div class="post-metadata">

**Author:** ![k5map](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/k5map/32/47681_2.png) [@k5map](https://discourse.nodered.org/u/k5map)\
**Post date:** [23 June 2023 11:58 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/3 "2023-06-23T11:58:42Z")

</div>

Interesting because I haven't opened a Github issue. But since my post, I've heard from fellow ham radio NR users (who use the same node) they are experiencing the same issue. So I suspect one of them opened the issue on Github. Somewhat pleased to hear its not just me 🙂 so fingers crossed the developer will release a fix.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [23 June 2023 17:19 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/4 "2023-06-23T17:19:38Z")

</div>

Haha, sorry, the id on GitHub looked similar and the time was so close. Hopefully the author will help out.

---

<div class="post-metadata">

**Author:** ![hazymat](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hazymat/32/108159_2.png) [@hazymat](https://discourse.nodered.org/u/hazymat)\
**Post date:** [25 June 2023 23:00 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/5 "2023-06-25T23:00:45Z")

</div>

FYI I am happily using Speedtest and it continues to work without error. I'm running it hourly and logging to Influx DB.

That said, the speedtest I am using doesn't have a configuration node. I'm using node-red-contrib-speedtest 1.1.0 and it works well.

Hope that helps?

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [26 June 2023 09:15 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/6 "2023-06-26T09:15:42Z")

</div>

@hazymat Mat, can you provide some other info:

1. what device and OS is it running?
2. what version of Node-RED and node.js

That could be a big help in figuring out what is happening because on my  
Pi 3 Model B Rev 1.2 running Buster  
NR v2.1.1 and node.js v14.21.3

using node-red-contrib-speedtest v1.1.0

I get `Error: Configuration - Could not retrieve or read configuration (ConfigurationError)`

---

<div class="post-metadata">

**Author:** ![hazymat](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hazymat/32/108159_2.png) [@hazymat](https://discourse.nodered.org/u/hazymat)\
**Post date:** [26 June 2023 23:13 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/7 "2023-06-26T23:13:52Z")

</div>

> [@zenofmud](#):
>
> - what device and OS is it running?
> - what version of Node-RED and node.js

Ubuntu 20.04.5 (running within a virtual machine on Win Hyper-V)  
NR v3.0.2 (you should upgrade!)  
node.js v17.5.0

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [27 June 2023 07:48 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/8 "2023-06-27T07:48:19Z")

</div>

> [@hazymat](#):
>
> node.js v17.5.0

Odd numbered node JS are not supported. You should use node 16 or 18 LTS

do you have `nvm` or `n` node version manager installed?

---

<div class="post-metadata">

**Author:** ![hazymat](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hazymat/32/108159_2.png) [@hazymat](https://discourse.nodered.org/u/hazymat)\
**Post date:** [27 June 2023 09:28 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/9 "2023-06-27T09:28:06Z")

</div>

I have nvm yes. Okay thanks - I had no idea. I'll upgrade to 18.16.1

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [27 June 2023 10:22 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/10 "2023-06-27T10:22:59Z")

</div>

> [@hazymat](#):
>
> I have nvm yes.

I suggest getting rid of it, it just causes confusion. Note, that is nvm not npm.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [27 June 2023 10:40 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/11 "2023-06-27T10:40:21Z")

</div>

> [@hazymat](#):
>
> NR v3.0.2 (you should upgrade!)

It is a test pi that I was trying it on.

@k5map

1. what device and OS are you using?
2. what version of Node-RED and node.js

---

<div class="post-metadata">

**Author:** ![k5map](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/k5map/32/47681_2.png) [@k5map](https://discourse.nodered.org/u/k5map)\
**Post date:** [27 June 2023 11:45 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/12 "2023-06-27T11:45:48Z")

</div>

RaspiOS 11 v5.10.0 (virtual machine)  
Node v16.20.1  
NPM v8.19.4  
NR v3.0.2

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [26 August 2023 11:46 UTC](https://discourse.nodered.org/t/node-red-contrib-speedtest-config-error/79358/13 "2023-08-26T11:46:27Z")

</div>

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