# Nodered : Webex : Can't read from server. It may not have the appropriate access-control-origin settings

**URL:** <https://discourse.nodered.org/t/nodered-webex-cant-read-from-server-it-may-not-have-the-appropriate-access-control-origin-settings/92858>\
**Category:** General\
**Created:** [1 November 2024 19:03 UTC](https://discourse.nodered.org/t/nodered-webex-cant-read-from-server-it-may-not-have-the-appropriate-access-control-origin-settings/92858 "2024-11-01T19:03:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neutrino2019](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/neutrino2019/32/96034_2.png) [@Neutrino2019](https://discourse.nodered.org/u/Neutrino2019)\
**Post date:** [1 November 2024 19:03 UTC](https://discourse.nodered.org/t/nodered-webex-cant-read-from-server-it-may-not-have-the-appropriate-access-control-origin-settings/92858/1 "2024-11-01T19:03:07Z")

</div>

Hi, there is a bug i got when using the library "node-red-contrib-spark". Precisely the "api" node from Webex. When i use it and compile the program, the server stops and try to restart on loop. But each time it throw the same error. I don't have access to Nodered anymore.

```auto
Can't read from server. It may not have the appropriate access-control-origin settings.

```

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/f/6fb5e1a373466e03084c7c042375e9cd5a5005e9.png)

I tried to decomment `httpNodeCors` section in `settings.js`, if it's a cors problem, but it didn't resolve anything.

To fix the restart issue, i edited the `~/.node-red/flows.js` in order to remove the problematic Webex node. And after that, Nodered works correcly.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/8/8892fe6921e5045c1c6df0563b0a60d87382c786.png)

But I don't know why the Webex node breaks Nodered server and if it's a library-related problem.

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [2 November 2024 17:53 UTC](https://discourse.nodered.org/t/nodered-webex-cant-read-from-server-it-may-not-have-the-appropriate-access-control-origin-settings/92858/2 "2024-11-02T17:53:55Z")

</div>

So this node looks to be abandoned, (not updated in over 6 years).

Looking on git hub this issue was reported 4 years ago without any resolution

> <https://github.com/nmarus/node-red-contrib-spark/issues/8>
>
> Hi,
> 
> I was playing in the past with this plugin long time ago. It was working …for me but then I didnt need it anymore.
> 
> Now I started again to play with it but now I have big issues, that the Plugin is crashing my Node Red Server and I have no idea why. After it crashes, I need to manually remove the Plugin via the Server CLI in order to get the Node Red Docker up and running again.
> 
> Unfortunatley I was not able to find any usefull information in any logs.
> 
> Br,
> Johannes

So I think you may need to look at another node or solution 😉

---

<div class="post-metadata">

**Author:** ![Neutrino2019](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/neutrino2019/32/96034_2.png) [@Neutrino2019](https://discourse.nodered.org/u/Neutrino2019)\
**Post date:** [8 November 2024 21:21 UTC](https://discourse.nodered.org/t/nodered-webex-cant-read-from-server-it-may-not-have-the-appropriate-access-control-origin-settings/92858/3 "2024-11-08T21:21:49Z")

</div>

Thank you!

---

<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:** [22 November 2024 21:22 UTC](https://discourse.nodered.org/t/nodered-webex-cant-read-from-server-it-may-not-have-the-appropriate-access-control-origin-settings/92858/4 "2024-11-22T21:22:29Z")

</div>

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