# Node-RED on AWS Elastic Beanstalk - unable to install new nodes, getting npm permissions error

**URL:** <https://discourse.nodered.org/t/node-red-on-aws-elastic-beanstalk-unable-to-install-new-nodes-getting-npm-permissions-error/32122>\
**Category:** General\
**Created:** [27 August 2020 23:49 UTC](https://discourse.nodered.org/t/node-red-on-aws-elastic-beanstalk-unable-to-install-new-nodes-getting-npm-permissions-error/32122 "2020-08-27T23:49:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicholas](https://avatars.discourse-cdn.com/v4/letter/n/4da419/32.png) [@nicholas](https://discourse.nodered.org/u/nicholas)\
**Post date:** [27 August 2020 23:49 UTC](https://discourse.nodered.org/t/node-red-on-aws-elastic-beanstalk-unable-to-install-new-nodes-getting-npm-permissions-error/32122/1 "2020-08-27T23:49:57Z")

</div>

Howdy folks!

I have an install of Node-RED running on Elastic Beanstalk, which I did following toconuts' tutorial linked below:

> **[toconuts/eb-node-red](https://github.com/toconuts/eb-node-red)**
>
> Node-RED for AWS Elastic Beanstalk. Contribute to toconuts/eb-node-red development by creating an account on GitHub.

However, when I try to install new nodes via "Manage palette," the install fails with OS-level npm permission errors (as shown in log except below).

I tried getting around this by updating package.json with the nodes that I require, but when I deploy this as a new app version, the nodes do not appear (presumably because package.json is not being reloaded for some reason? -- probably a separate issue)

I have been working with AWS dev support on this issue, but so far they are under the impression that this is an application-level issue and therefore out of their scope --

Any and all insights / guidance y'all might have on this topic will be much appreciated!

-Nicholas

excerpts from the error log showing typical error below :

1:40:59.630Z [err] errno  
2020-08-26T21:40:59.630Z [err] -13  
2020-08-26T21:40:59.630Z [err] npm  
2020-08-26T21:40:59.630Z [err]  
2020-08-26T21:40:59.630Z [err] ERR!  
2020-08-26T21:40:59.630Z [err]  
2020-08-26T21:40:59.630Z [err] syscall  
2020-08-26T21:40:59.630Z [err] access  
2020-08-26T21:40:59.631Z [err] npm  
2020-08-26T21:40:59.631Z [err]  
2020-08-26T21:40:59.632Z [err] ERR!  
2020-08-26T21:40:59.632Z [err] Error: EACCES: permission denied, access '/var/app/current/node\_modules/node-red'  
2020-08-26T21:40:59.632Z [err] npm  
2020-08-26T21:40:59.632Z [err]  
2020-08-26T21:40:59.632Z [err] ERR!  
2020-08-26T21:40:59.632Z [err] [Error: EACCES: permission denied, access '/var/app/current/node\_modules/node-red'] {  
2020-08-26T21:40:59.632Z [err] npm  
2020-08-26T21:40:59.632Z [err]  
2020-08-26T21:40:59.632Z [err] ERR!  
2020-08-26T21:40:59.632Z [err] stack: "Error: EACCES: permission denied, access '/var/app/current/node\_modules/node-red'",

---

<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:** [28 August 2020 09:40 UTC](https://discourse.nodered.org/t/node-red-on-aws-elastic-beanstalk-unable-to-install-new-nodes-getting-npm-permissions-error/32122/2 "2020-08-28T09:40:21Z")

</div>

You should open an issue with toconut on GitHub.

---

<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:** [27 October 2020 09:40 UTC](https://discourse.nodered.org/t/node-red-on-aws-elastic-beanstalk-unable-to-install-new-nodes-getting-npm-permissions-error/32122/3 "2020-10-27T09:40:30Z")

</div>

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