# Problem with node-red-contrib-ui-led not showing in pallete
**URL:** https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547
**Category:** General
**Created:** [14 August 2020 07:11 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547 "2020-08-14T07:11:51Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@uNodem](https://discourse.nodered.org/u/uNodem)
#### Post date: [14 August 2020 07:11 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/1 "2020-08-14T07:11:52Z")
Hello together,
I would like to export a project and import it on another PC. Unfortunately, a new version of libraries is installed on the second computer, which prevents import. Is it possible to install an older version of the libraries or does someone like another idea? I get the following error message:
2020-08-14T07:10:26.307Z installieren : node-red-contrib-ui-led 0.3.3
2020-08-14T07:10:34.704Z npm.cmd install --no-audit --no-update-notifier --no-fund --save --save-prefix="~" --production node-red-contrib-ui-led@0.3.3
2020-08-14T07:10:36.894Z [err] npm
2020-08-14T07:10:36.894Z [err] WARN registry Unexpected warning for [https://registry.npmjs.org/:](https://registry.npmjs.org/:) Miscellaneous Warning UNABLE\_TO\_GET\_ISSUER\_CERT\_LOCALLY: request to [https://registry.npmjs.org/node-red-contrib-ui-led](https://registry.npmjs.org/node-red-contrib-ui-led) failed, reason: unable to get local issuer certificate
2020-08-14T07:10:36.894Z [err] npm
2020-08-14T07:10:36.894Z [err] WARN registry
2020-08-14T07:10:36.894Z [err] Using stale data from [https://registry.npmjs.org/](https://registry.npmjs.org/) due to a request error during revalidation.
2020-08-14T07:10:37.071Z [err] npm ERR!
2020-08-14T07:10:37.071Z [err] code UNABLE\_TO\_GET\_ISSUER\_CERT\_LOCALLY
2020-08-14T07:10:37.071Z [err] npm ERR! errno UNABLE\_TO\_GET\_ISSUER\_CERT\_LOCALLY
2020-08-14T07:10:37.072Z [err] npm ERR! request to [https://registry.npmjs.org/node-red-contrib-ui-led](https://registry.npmjs.org/node-red-contrib-ui-led) failed, reason: unable to get local issuer certificate
2020-08-14T07:10:37.078Z [err]
2020-08-14T07:10:37.078Z [err] npm
2020-08-14T07:10:37.078Z [err] ERR! A complete log of this run can be found in:
2020-08-14T07:10:37.078Z [err] npm ERR! C:\Users\uhmvcw\AppData\Roaming\npm-cache\_logs\2020-08-14T07\_10\_37\_072Z-debug.log
2020-08-14T07:10:37.097Z rc=1
Thank you for your help
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [14 August 2020 08:26 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/2 "2020-08-14T08:26:47Z")
> [@uNodem](#):
>
> Unfortunately, a new version of libraries is installed on the second computer, which prevents import.
I don't see what it is that makes you think that is the problem.
What do these commands show?
`node -v`
`npm -v`
However it might possibly have been a temporary problem with the npmjs website. Is it still failing?
What happens if, in a browser, you go to [https://registry.npmjs.org/node-red-contrib-ui-led](https://registry.npmjs.org/node-red-contrib-ui-led) ?
---
### Author:  [@uNodem](https://discourse.nodered.org/u/uNodem)
#### Post date: [14 August 2020 08:38 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/3 "2020-08-14T08:38:22Z")
source computer:
node -v shows: v12.18.0
npm-v shows: 6.14.4
target computer:
node -v shows: v14.4.0
npm-v shows: 6.14.5
yes I have had the problem since yesterday
the address shows something like a log file
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [14 August 2020 09:15 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/4 "2020-08-14T09:15:19Z")
That is not a library version problem. That could be resolved quite easily.
You have a Node.js version issue given that your target device is a whole major version ahead.
Also, as Colin has indicated, the error you are getting does not appear to be related to either a library nor the Node.js version. Instead it appears to be a problem of the target device not being able to connect to [npmjs.com](http://npmjs.com)
You will need to resolve that npm problem first. Can you manually install npm modules?
Once you have resolved that. The installation on the target should be simple enough as long as you copied over the settings.js and package.json files not just the flows and credentials files.
---
### Author:  [@uNodem](https://discourse.nodered.org/u/uNodem)
#### Post date: [14 August 2020 09:15 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/5 "2020-08-14T09:15:23Z")
if I want to run an update, the following message appears:
C:\Users\uhmvcw\>npm install -g --unsafe-perm node-red
npm WARN registry Unexpected warning for [https://registry.npmjs.org/:](https://registry.npmjs.org/:) Miscellaneous Warning UNABLE\_TO\_GET\_ISSUER\_CERT\_LOCALLY: request to [https://registry.npmjs.org/node-red](https://registry.npmjs.org/node-red) failed, reason: unable to get local issuer certificate
npm WARN registry Using stale data from [https://registry.npmjs.org/](https://registry.npmjs.org/) due to a request error during revalidation.
npm WARN deprecated request@2.88.0: request has been deprecated, see [https://github.com/request/request/issues/3142](https://github.com/request/request/issues/3142)
npm WARN deprecated bcrypt@3.0.8: versions \< v5.0.0 do not handle NUL in passwords properly
C:\Users\uhmvcw\AppData\Roaming\npm\node-red-pi -\> C:\Users\uhmvcw\AppData\Roaming\npm\node\_modules\node-red\bin\node-red-pi
C:\Users\uhmvcw\AppData\Roaming\npm\node-red -\> C:\Users\uhmvcw\AppData\Roaming\npm\node\_modules\node-red\red.js
- node-red@1.1.0
updated 1 package in 20.975s
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [14 August 2020 09:18 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/6 "2020-08-14T09:18:59Z")
> [@uNodem](#):
>
> npm WARN registry Unexpected warning for [https://registry.npmjs.org/:](https://registry.npmjs.org/:) Miscellaneous Warning UNABLE\_TO\_GET\_ISSUER\_CERT\_LOCALLY: request to [https://registry.npmjs.org/node-red](https://registry.npmjs.org/node-red) failed, reason: unable to get local issuer certificate
A quick internet search suggests that you should run `npm cache verify`.
You could also try `npm cache clear --force` (ignore the warning, it is fine).
---
### Author:  [@uNodem](https://discourse.nodered.org/u/uNodem)
#### Post date: [14 August 2020 09:30 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/7 "2020-08-14T09:30:17Z")
after npm cache clear --force I have the following error when trying update:
C:\Users\uhmvcw\>npm install -g --unsafe-perm node-red
npm ERR! code UNABLE\_TO\_GET\_ISSUER\_CERT\_LOCALLY
npm ERR! errno UNABLE\_TO\_GET\_ISSUER\_CERT\_LOCALLY
npm ERR! request to [https://registry.npmjs.org/node-red](https://registry.npmjs.org/node-red) failed, reason: unable to get local issuer certificate
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\uhmvcw\AppData\Roaming\npm-cache\_logs\2020-08-14T09\_28\_34\_851Z-debug.log
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [14 August 2020 09:35 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/8 "2020-08-14T09:35:00Z")
Assuming you haven't done anything odd, to install a package globally you need to use `sudo`.
Not sure if there is a global version of the cache - I think that there is, so you probably also need to clear the global cache as well.
---
### Author:  [@uNodem](https://discourse.nodered.org/u/uNodem)
#### Post date: [14 August 2020 09:40 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/9 "2020-08-14T09:40:05Z")
I can't use the command sudo because I use windows
---
### Author:  [@UnborN](https://discourse.nodered.org/u/UnborN)
#### Post date: [14 August 2020 09:45 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/10 "2020-08-14T09:45:33Z")
Sometimes there are certificate issues due to date time mismatch
out of curiosity is the clock / date / timezone set correctly on the pc ?
---
### Author:  [@uNodem](https://discourse.nodered.org/u/uNodem)
#### Post date: [14 August 2020 09:53 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/11 "2020-08-14T09:53:34Z")
yes, this is correct
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [14 August 2020 10:12 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/12 "2020-08-14T10:12:47Z")
Try
`npm -g cache clear --force`
---
### Author:  [@uNodem](https://discourse.nodered.org/u/uNodem)
#### Post date: [14 August 2020 10:34 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/13 "2020-08-14T10:34:22Z")
@colin i've tried it
I have now reinstalled [node.js](https://ssl.microsofttranslator.com/bv.aspx?ref=TAns&from=&to=en&a=node.js) and the same version on both computers. unfortunately, individual flows are still not recognized. I still can't update my libraries.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [14 August 2020 10:50 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/14 "2020-08-14T10:50:27Z")
> [@uNodem](#):
>
> individual flows are still not recognized. I still can't update my libraries.
More detail please. What do you mean flows are not recognised, what error are you getting when you use npm?
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [14 August 2020 10:56 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/15 "2020-08-14T10:56:47Z")
> [@uNodem](#):
>
> can't use the command sudo because I use windows
The equivelant on windows is right click runas administrator (even if the account is an administrator account)
> [@uNodem](#):
>
> npm ERR! code UNABLE\_TO\_GET\_ISSUER\_CERT\_LOCALLY
on an administrative cmd prompt, do this...
```bash
npm config set strict-ssl false
REM now try again
npm install -g --unsafe-perm node-red
```
---
### Author:  [@UnborN](https://discourse.nodered.org/u/UnborN)
#### Post date: [16 August 2020 01:09 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/16 "2020-08-16T01:09:09Z")
@uNodem are you using command prompt or powershell ?
there is an article [here](https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/Npm-ERR-code-UNABLE-TO-GET-ISSUER-CERT-LOCALLY-when-installing-NPM-packages-for-Forge-platform-using-Powershell.html) that describes some issue with powershell
1. in case you were using powershell try command prompt as admin
2. also the recommened solution based on the above article was to run
`npm config set registry http://registry.npmjs.org/`
ps. i dont know if its correct to change the registry from https to http but you can give it a try
---
### Author:  [@uNodem](https://discourse.nodered.org/u/uNodem)
#### Post date: [17 August 2020 07:40 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/17 "2020-08-17T07:40:32Z")
@UnborN thank you, this has solved it and I can now update.
---
### Author:  [@uNodem](https://discourse.nodered.org/u/uNodem)
#### Post date: [17 August 2020 07:50 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/18 "2020-08-17T07:50:16Z")
Now I have only one last problem. I can't install two pallete, or if I install them it doesn't appear on the left in the bar. These are the two libraries where I had difficulty importing.
---
### Author:  [@UnborN](https://discourse.nodered.org/u/UnborN)
#### Post date: [17 August 2020 09:18 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/19 "2020-08-17T09:18:27Z")
1. what method did you use to install them?
According to the [docs](https://nodered.org/docs/user-guide/runtime/adding-nodes) you can use npm in the `.node-red` folder or directly within the editor by selecting the `Manage Palette`
2. did you get any error messages ?
3. did you try to restart node-red and refresh your browser ? (hard refresh - delete browser cache)
---
### Author:  [@uNodem](https://discourse.nodered.org/u/uNodem)
#### Post date: [17 August 2020 11:20 UTC](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547/20 "2020-08-17T11:20:27Z")
1. I tried it out via the editor as well as via the cmd prompt.
2. C:\Users\XXX\>npm install node-red-contrib-ui-led
npm WARN [XXX@1.0.0](mailto:moritz@1.0.0) No description
npm WARN [XXX@1.0.0](mailto:moritz@1.0.0) No repository field.
- [node-red-contrib-ui-led@0.3.3](mailto:node-red-contrib-ui-led@0.3.3)
updated 1 package and audited 81 packages in 1.042s
found 0 vulnerabilities
1. yes, I tried that too. I have also completely reinstalled node red
[Next page](https://discourse.nodered.org/t/problem-with-node-red-contrib-ui-led-not-showing-in-pallete/31547.md?page=2)