# Node-red multi-user workaround

**URL:** <https://discourse.nodered.org/t/node-red-multi-user-workaround/24881>\
**Category:** General\
**Created:** [15 April 2020 15:03 UTC](https://discourse.nodered.org/t/node-red-multi-user-workaround/24881 "2020-04-15T15:03:26Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [15 April 2020 22:56 UTC](https://discourse.nodered.org/t/node-red-multi-user-workaround/24881/4 "2020-04-15T22:56:09Z")

</div>

It is incredibly easy to run multiple instances (docker is a new world of hurt if you're not using it already)

See this...

> [@Node red multiple instances](https://discourse.nodered.org/t/node-red-multiple-instances/9787/5):
>
> Instead of changing settings file, I use the -p command line option to specify the port. I also use nssm on windows for multiple instances. So each service launches for example... node-red -p 1881 -u c:/nr1881 node-red -p 1882 -u c:/nr1882 And so on. BTW, @knolleary that document you linked to doesn't show the -p option or -t option.

---

_[View the full topic](https://discourse.nodered.org/t/node-red-multi-user-workaround/24881)._