# Node-Red on Synology

**URL:** <https://discourse.nodered.org/t/node-red-on-synology/3762>\
**Category:** General\
**Created:** [7 October 2018 18:28 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762 "2018-10-07T18:28:27Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ohaldi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ohaldi/32/3017_2.png) [@ohaldi](https://discourse.nodered.org/u/ohaldi)\
**Post date:** [7 October 2018 18:28 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/1 "2018-10-07T18:28:27Z")

</div>

Hello,  
Did somebody wrote a good instruction how to install Node-RED on a Synology NAS?  
I'm not very good at linux.  
Regards  
Otto

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [7 October 2018 18:59 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/2 "2018-10-07T18:59:45Z")

</div>

Depends on your NAS and its capabilities e.g. if you want to use Docker  
But try [https://www.rs-online.com/designspark/installing-node-red-on-a-synology-nas](https://www.rs-online.com/designspark/installing-node-red-on-a-synology-nas)

(the first hit on google for "Node-red synology install)

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [7 October 2018 19:47 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/3 "2018-10-07T19:47:33Z")

</div>

I can't really recommend docker on the Synology NAS's unless you have one with a good amount of memory. However, it should work OK as long as you don't try to do too much with it. It is certainly the easiest way to get started as long as you have a NAS that will run docker (not all of them will).

I think that there is a 3rd party NodeJS package for them which would be your other starting point. However, the disadvantage of this approach is that you will likely need to get a bit more familiar not just with Linux but with the way that the Synology NAS uses Linux since Synology don't really want you messing around with the command line.

Personally, though I have one and though it can run Docker - and I have done - I'm already doing quite a lot with my NAS and though I've upgraded the RAM, it still gets bogged down with big backup jobs. So I leave the NAS to do what it is good at - handling files - and use the Pi for Node-RED.

---

<div class="post-metadata">

**Author:** ![ohaldi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ohaldi/32/3017_2.png) [@ohaldi](https://discourse.nodered.org/u/ohaldi)\
**Post date:** [8 October 2018 20:10 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/4 "2018-10-08T20:10:05Z")

</div>

Many thanks for your help.  
The link from ukmoose will help me a lot. I can use docker with my DS214!

---

<div class="post-metadata">

**Author:** ![joachim198](https://avatars.discourse-cdn.com/v4/letter/j/35a633/32.png) [@joachim198](https://discourse.nodered.org/u/joachim198)\
**Post date:** [16 October 2018 06:45 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/5 "2018-10-16T06:45:07Z")

</div>

HI! I tried to install node-red on my synology ds115j. node.js ist running and works but when installing with  
"sudo npm install -g --unsafe-perm node-red" i get this?! Any ideas?

npm WARN deprecated mimelib@0.3.1: This project is unmaintained  
npm WARN deprecated mailcomposer@2.1.0: This project is unmaintained  
npm WARN deprecated buildmail@2.0.0: This project is unmaintained  
/volume1/@appstore/Node.js\_v8/usr/local/bin/node-red -\> /volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/red.js  
/volume1/@appstore/Node.js\_v8/usr/local/bin/node-red-pi -\> /volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/bin/node-red-pi

> bcrypt@2.0.1 install /volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt  
> node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(404): [https://github.com/kelektiv/node.bcrypt.js/releases/download/v2.0.1/bcrypt\_lib-v2.0.1-node-v57-linux-arm-unknown.tar.gz](https://github.com/kelektiv/node.bcrypt.js/releases/download/v2.0.1/bcrypt_lib-v2.0.1-node-v57-linux-arm-unknown.tar.gz)  
node-pre-gyp ERR! Pre-built binaries not found for bcrypt@2.0.1 and node@8.9.4 (node-v57 ABI, unknown) (falling back to source compile with node-gyp)  
gyp ERR! build error  
gyp ERR! stack Error: not found: make  
gyp ERR! stack at getNotFoundError (/usr/local/lib/node\_modules/npm/node\_modules/which/which.js:13:12)  
gyp ERR! stack at F (/usr/local/lib/node\_modules/npm/node\_modules/which/which.js:68:19)  
gyp ERR! stack at E (/usr/local/lib/node\_modules/npm/node\_modules/which/which.js:80:29)  
gyp ERR! stack at /usr/local/lib/node\_modules/npm/node\_modules/which/which.js:89:16  
gyp ERR! stack at /usr/local/lib/node\_modules/npm/node\_modules/which/node\_modules/isexe/index.js:42:5  
gyp ERR! stack at /usr/local/lib/node\_modules/npm/node\_modules/which/node\_modules/isexe/mode.js:8:5  
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21)  
gyp ERR! System Linux 3.2.40  
gyp ERR! command "/volume1/@appstore/Node.js\_v8/usr/local/bin/node" "/usr/local/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js" "build" "--fallback- to-build" "--module=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding/bcrypt\_lib.node" "--module\_name=bcrypt\_lib " "--module\_path=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding" "--napi\_version=1" "--node\_abi\_napi=napi"  
gyp ERR! cwd /volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt  
gyp ERR! node -v v8.9.4  
gyp ERR! node-gyp -v v3.6.2  
gyp ERR! not ok  
node-pre-gyp ERR! build error  
node-pre-gyp ERR! stack Error: Failed to execute '/volume1/@appstore/Node.js\_v8/usr/local/bin/node /usr/local/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding/bcrypt\_lib.node -- module\_name=bcrypt\_lib --module\_path=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding --napi\_version=1 --node\_abi\_napi=napi' (1)  
node-pre-gyp ERR! stack at ChildProcess. (/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/node\_modules/node -pre-gyp/lib/util/compile.js:83:29)  
node-pre-gyp ERR! stack at emitTwo (events.js:126:13)  
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:214:7)  
node-pre-gyp ERR! stack at maybeClose (internal/child\_process.js:925:16)  
node-pre-gyp ERR! stack at Process.ChildProcess.\_handle.onexit (internal/child\_process.js:209:5)  
node-pre-gyp ERR! System Linux 3.2.40  
node-pre-gyp ERR! command "/volume1/@appstore/Node.js\_v8/usr/local/bin/node" "/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/node\_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"  
node-pre-gyp ERR! cwd /volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt  
node-pre-gyp ERR! node -v v8.9.4  
node-pre-gyp ERR! node-pre-gyp -v v0.9.1  
node-pre-gyp ERR! not ok  
Failed to execute '/volume1/@appstore/Node.js\_v8/usr/local/bin/node /usr/local/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js build --fallback-to-bu ild --module=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding/bcrypt\_lib.node --module\_name=bcrypt\_lib --module \_path=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding --napi\_version=1 --node\_abi\_napi=napi' (1)  
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bcrypt@2.0.1 (node\_modules/node-red/node\_modules/bcrypt):  
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bcrypt@2.0.1 install: `node-pre-gyp install --fallback-to-build`  
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

- node-red@0.19.4  
added 321 packages in 197.725s

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [16 October 2018 07:24 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/6 "2018-10-16T07:24:07Z")

</div>

Hi guys,  
I've got a couple of QNAP NAS units.  
I assume that I can use the same procedure to install Node-RED using Docker on a QNAP ???  
Or is there a better way/method to get Node-RED and Mosquitto up and running on a QNAP???

Cheers from David

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [17 October 2018 15:27 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/7 "2018-10-17T15:27:48Z")

</div>

You seem to be missing the Linux build utils so the compile fails for gyp.

If you have a NAS with sufficient memory and the right processor, you should be able to use Docker on either QNAP or Synology.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [17 October 2018 21:06 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/8 "2018-10-17T21:06:30Z")

</div>

@joachim198 - did that actually fail in the end ? It WARNed about an optional bcrypt dependancy - but may have succeeded at the end.

---

<div class="post-metadata">

**Author:** ![ohaldi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ohaldi/32/3017_2.png) [@ohaldi](https://discourse.nodered.org/u/ohaldi)\
**Post date:** [27 October 2018 15:56 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/9 "2018-10-27T15:56:08Z")

</div>

Hello Node-Red work well on my Synology.  
But as soon I close the Putty remote connection the Node-RED process stop.

To start Node-Red I do this : /volume2/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/nod.js  
How I can I keep the process alive? Sorry I'm not at home with linux...  
Regards  
Otto

# Welcome to Node-RED

27 Oct 17:21:13 - [info] Node-RED version: v0.19.4  
27 Oct 17:21:13 - [info] Node.js version: v8.9.4  
27 Oct 17:21:13 - [info] Linux 3.2.40 arm LE  
27 Oct 17:21:18 - [info] Loading palette nodes  
27 Oct 17:21:20 - [warn] rpi-gpio : Raspberry Pi specific node set inactive  
27 Oct 17:21:21 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library  
27 Oct 17:21:27 - [info] Settings file : /var/services/homes/admin/.node-red/settings.js  
27 Oct 17:21:27 - [info] Context store : 'default' [module=memory]  
27 Oct 17:21:27 - [info] User directory : /var/services/homes/admin/.node-red  
27 Oct 17:21:27 - [warn] Projects disabled : editorTheme.projects.enabled=false  
27 Oct 17:21:27 - [info] Flows file : /var/services/homes/admin/.node-red/flows\_SERLIX.json  
27 Oct 17:21:27 - [info] Creating new flow file  
27 Oct 17:21:27 - [warn]

* * *

Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials  
file will not be recoverable, you will have to delete it and re-enter  
your credentials.

## You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

27 Oct 17:21:27 - [info] Starting flows  
27 Oct 17:21:27 - [info] Started flows  
27 Oct 17:21:28 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [27 October 2018 16:46 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/10 "2018-10-27T16:46:18Z")

</div>

if you have installed Node-RED directly on your synology box following the instructions I linked to above the instructions include a section on how to make Node-RED autostart

---

<div class="post-metadata">

**Author:** ![gozilla01](https://avatars.discourse-cdn.com/v4/letter/g/db5fbb/32.png) [@gozilla01](https://discourse.nodered.org/u/gozilla01)\
**Post date:** [3 December 2018 21:43 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/11 "2018-12-03T21:43:38Z")

</div>

@ukmoose  
Hello,  
I have nas synology DS216J, I installed OpenHab is it works.  
I would also like to install node-red, I followed your guide I have an error, I do not know how to move forward  
I would not do mess!  
A help .. thanks

> **sudo npm install -g --unsafe-perm node-red**  
> npm WARN deprecated nodemailer@1.11.0: All versions below 4.0.1 of Nodemailer are deprecated. See [Status :: Nodemailer](https://nodemailer.com/status/)  
> npm WARN deprecated mailparser@0.6.2: Mailparser versions older than v2.3.0 are deprecated  
> npm WARN deprecated mimelib@0.3.1: This project is unmaintained  
> npm WARN deprecated mailcomposer@2.1.0: This project is unmaintained  
> npm WARN deprecated buildmail@2.0.0: This project is unmaintained  
> /volume1/@appstore/Node.js\_v8/usr/local/bin/node-red -\> /volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/red.js  
> /volume1/@appstore/Node.js\_v8/usr/local/bin/node-red-pi -\> /volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/bin/node-red-pi

> bcrypt@2.0.1 install /volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt  
> node-pre-gyp install --fallback-to-build  
> node-pre-gyp ERR! Tried to download(404): [https://github.com/kelektiv/node.bcrypt.js/releases/download/v2.0.1/bcrypt\_lib-v2.0.1-node-v57-linux-arm-unknown.tar.gz](https://github.com/kelektiv/node.bcrypt.js/releases/download/v2.0.1/bcrypt_lib-v2.0.1-node-v57-linux-arm-unknown.tar.gz)  
> node-pre-gyp ERR! Pre-built binaries not found for bcrypt@2.0.1 and node@8.9.4 (node-v57 ABI, unknown) (falling back to source compile with node-gyp)  
> gyp ERR! build error  
> gyp ERR! stack Error: not found: make  
> gyp ERR! stack at getNotFoundError (/usr/local/lib/node\_modules/npm/node\_modules/which/which.js:13:12)  
> gyp ERR! stack at F (/usr/local/lib/node\_modules/npm/node\_modules/which/which.js:68:19)  
> gyp ERR! stack at E (/usr/local/lib/node\_modules/npm/node\_modules/which/which.js:80:29)  
> gyp ERR! stack at /usr/local/lib/node\_modules/npm/node\_modules/which/which.js:89:16  
> gyp ERR! stack at /usr/local/lib/node\_modules/npm/node\_modules/which/node\_modules/isexe/index.js:42:5  
> gyp ERR! stack at /usr/local/lib/node\_modules/npm/node\_modules/which/node\_modules/isexe/mode.js:8:5  
> gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21)  
> gyp ERR! System Linux 3.10.105  
> gyp ERR! command "/volume1/@appstore/Node.js\_v8/usr/local/bin/node" "/usr/local/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding/bcrypt\_lib.node" "--module\_name=bcrypt\_lib" "--module\_path=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding" "--napi\_version=1" "--node\_abi\_napi=napi"  
> gyp ERR! cwd /volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt  
> gyp ERR! node -v v8.9.4  
> gyp ERR! node-gyp -v v3.6.2  
> gyp ERR! not ok  
> node-pre-gyp ERR! build error  
> node-pre-gyp ERR! stack Error: Failed to execute '/volume1/@appstore/Node.js\_v8/usr/local/bin/node /usr/local/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding/bcrypt\_lib.node --module\_name=bcrypt\_lib --module\_path=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding --napi\_version=1 --node\_abi\_napi=napi' (1)  
> node-pre-gyp ERR! stack at ChildProcess. (/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/node\_modules/node-pre-gyp/lib/util/compile.js:83:29)  
> node-pre-gyp ERR! stack at emitTwo (events.js:126:13)  
> node-pre-gyp ERR! stack at ChildProcess.emit (events.js:214:7)  
> node-pre-gyp ERR! stack at maybeClose (internal/child\_process.js:925:16)  
> node-pre-gyp ERR! stack at Process.ChildProcess.\_handle.onexit (internal/child\_process.js:209:5)  
> node-pre-gyp ERR! System Linux 3.10.105  
> node-pre-gyp ERR! command "/volume1/@appstore/Node.js\_v8/usr/local/bin/node" "/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/node\_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"  
> node-pre-gyp ERR! cwd /volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt  
> node-pre-gyp ERR! node -v v8.9.4  
> node-pre-gyp ERR! node-pre-gyp -v v0.9.1  
> node-pre-gyp ERR! not ok  
> Failed to execute '/volume1/@appstore/Node.js\_v8/usr/local/bin/node /usr/local/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding/bcrypt\_lib.node --module\_name=bcrypt\_lib --module\_path=/volume1/@appstore/Node.js\_v8/usr/local/lib/node\_modules/node-red/node\_modules/bcrypt/lib/binding --napi\_version=1 --node\_abi\_napi=napi' (1)  
> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bcrypt@2.0.1 (node\_modules/node-red/node\_modules/bcrypt):  
> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bcrypt@2.0.1 install: `node-pre-gyp install --fallback-to-build`  
> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1  
> +node-red@0.19.5  
> updated 1 package in 35.667s

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [3 December 2018 22:27 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/12 "2018-12-03T22:27:06Z")

</div>

> [@gozilla01](#):
>
> I have an error

The error is that you are missing some low-level tools that allow you to build (compile) one of the components in Node-RED - `bcrypt`. However, that is an optional compile and it should still work. Have you tried running it?

---

<div class="post-metadata">

**Author:** ![gozilla01](https://avatars.discourse-cdn.com/v4/letter/g/db5fbb/32.png) [@gozilla01](https://discourse.nodered.org/u/gozilla01)\
**Post date:** [3 December 2018 22:38 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/13 "2018-12-03T22:38:50Z")

</div>

I do not know how.  
Can you give me directions?

---

<div class="post-metadata">

**Author:** ![luisgcu](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/luisgcu/32/4549_2.png) [@luisgcu](https://discourse.nodered.org/u/luisgcu)\
**Post date:** [4 December 2018 02:42 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/14 "2018-12-04T02:42:24Z")

</div>

Hi ohaldi,  
I have synology DS 718 and I installed docker on it , and is very easy, you can install several nodered instances

On synology package center install docker.

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

* * *

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

then: click in image, double click node-red docker image and before going to advanced settings you can chance the container name if you like.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/b/b93a0ccec54ee8a82c6f424eaa4d4a1a0122fd8f.png)  
Set desired local port:  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/f/f1f40691a5a629115c7b04a665654269c17dd922.png)  
next:  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/f/fde74fd20cea65e388ee9e6bf37b72541fa9e810.png)  
go to overview you will see all your containers running.  
you can install node-red docker image from the SSH interface if you like  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/5/5c12f569fdc20f83c6fd80d6e0e371758b9faa14.png)

---

<div class="post-metadata">

**Author:** ![luisgcu](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/luisgcu/32/4549_2.png) [@luisgcu](https://discourse.nodered.org/u/luisgcu)\
**Post date:** [4 December 2018 02:45 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/15 "2018-12-04T02:45:29Z")

</div>

I had that problem a year ago.. then appear dockers!! since then every piece of software that install on my nas is using docker

---

<div class="post-metadata">

**Author:** ![luisgcu](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/luisgcu/32/4549_2.png) [@luisgcu](https://discourse.nodered.org/u/luisgcu)\
**Post date:** [4 December 2018 02:51 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/16 "2018-12-04T02:51:18Z")

</div>

Intially my synology nas has only 2gb of ram, and I have several node-red instances running , no problem.. it works very well.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [4 December 2018 07:19 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/17 "2018-12-04T07:19:20Z")

</div>

> [@luisgcu](#):
>
> Intially my synology nas has only 2gb of ram, and I have several node-red instances running , no problem.. it works very well.

Indeed. Sadly, I also use my NAS as a NAS with a couple of TB of data. This runs fine most of the time. But when it needs to index and when it needs to run backups, it rapidly grinds to a halt if you aren't careful.

So it just depends what you are running on it.

---

<div class="post-metadata">

**Author:** ![mdegeest](https://avatars.discourse-cdn.com/v4/letter/m/b3f665/32.png) [@mdegeest](https://discourse.nodered.org/u/mdegeest)\
**Post date:** [27 December 2018 20:36 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/19 "2018-12-27T20:36:20Z")

</div>

Hi Joachim198,

I'm trying to install node-red on a DS214play and I get exactly the same error (bcrypt related).  
Where you able to solve this issue?  
Can you please share how?

Thank you!

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [27 December 2018 21:11 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/20 "2018-12-27T21:11:38Z")

</div>

There was a warning not an error.. Are you sure you have an error ?

---

<div class="post-metadata">

**Author:** ![trlafleur](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trlafleur/32/47662_2.png) [@trlafleur](https://discourse.nodered.org/u/trlafleur)\
**Post date:** [23 January 2019 17:34 UTC](https://discourse.nodered.org/t/node-red-on-synology/3762/21 "2019-01-23T17:34:27Z")

</div>

You might want to look at this install...

[https://www.rs-online.com/designspark/installing-node-red-on-a-synology-nas](https://www.rs-online.com/designspark/installing-node-red-on-a-synology-nas)

[Next page](https://discourse.nodered.org/t/node-red-on-synology/3762.md?page=2)