# Troubleshooting an error on IBM cloud

**URL:** <https://discourse.nodered.org/t/troubleshooting-an-error-on-ibm-cloud/16877>\
**Category:** General\
**Created:** [19 October 2019 07:46 UTC](https://discourse.nodered.org/t/troubleshooting-an-error-on-ibm-cloud/16877 "2019-10-19T07:46:14Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [22 October 2019 20:46 UTC](https://discourse.nodered.org/t/troubleshooting-an-error-on-ibm-cloud/16877/9 "2019-10-22T20:46:50Z")

</div>

> [@knolleary](#):
>
> Have you added `node-red-dashboard` through the palette manager

Yes I had installed it via the pallette manager.

> [@knolleary](#):
>
> whenever the app is restaged

Ah that explains a couple of things ...  
This evening I had published a new version of my heatmap node on NPM, and updated it via the palette manager on IBM cloud. But then I got following error afterwards:

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/7/7d778c660038ecb9df83d745824d657770651438.png)

But as mentioned above, I use IBM cloud now for the first time (only to assist 1 single user). Have been reading a bit about it, but don't want to waste too much time on it ...

So I tried at last my own workaround to restart Node-RED _ **hard** _ way:

- I logged on to the SSH panel
- I did `ps -ef` to get the PID of the running node-red process
- The I executed a `kill` of that PID
- And immediately afterwards I had a Node-RED instance with my new heatmap code up and running

I assume your _ **soft** _ way is much better 😇  
Will try to do it via the package.json file...

---

_[View the full topic](https://discourse.nodered.org/t/troubleshooting-an-error-on-ibm-cloud/16877)._