# adminAuth not working windows 10

**URL:** <https://discourse.nodered.org/t/adminauth-not-working-windows-10/52521>\
**Category:** General\
**Created:** [21 October 2021 17:15 UTC](https://discourse.nodered.org/t/adminauth-not-working-windows-10/52521 "2021-10-21T17:15:03Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yonny24](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/yonny24/32/49675_2.png) [@Yonny24](https://discourse.nodered.org/u/Yonny24)\
**Post date:** [21 October 2021 17:15 UTC](https://discourse.nodered.org/t/adminauth-not-working-windows-10/52521/1 "2021-10-21T17:15:04Z")

</div>

I realise this has been asked before but on a very old thread.

I installed nodered with the windows 64bit installer package. node.js, npm installed all fine.  
'node-v16.11.1-x64.msi'  
Nodered service was created and runs as the local system account.

Only thing I cannot get to work is the login pop-up for credentials.

I have modified the settings.js underC:\Users\jon.node-red

Restarted, rebooted etc. Changes to the settings are persistent.

```auto
Welcome to Node-RED
===================

21 Oct 14:12:05 - [info] Node-RED version: v2.0.6
21 Oct 14:12:05 - [info] Node.js version: v16.11.1
21 Oct 14:12:05 - [info] Windows_NT 10.0.19043 x64 LE
21 Oct 14:12:06 - [info] Loading palette nodes
21 Oct 14:12:09 - [info] Settings file : C:\Users\jon\.node-red\settings.js

```

Can anyone suggest where I am going wrong? Perhaps a permission issue with the service running and not being able to read the settings file?

Thanks

---

<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:** [21 October 2021 19:33 UTC](https://discourse.nodered.org/t/adminauth-not-working-windows-10/52521/2 "2021-10-21T19:33:27Z")

</div>

> [@Yonny24](#):
>
> Nodered service was created and runs as the local system account

Unless you tell the service to run node-red with command line parameters, it will NOT be using that folder.

You have two choices...

1. create account "node-red" and run the service under that account - you will see that it creates `C:\Users\node-red\.node-red\settings.js` on first run
2. add command line parameters to tell the service to use the folder `C:\Users\jon\.node-red`

The docs tell you what the command line parameters are (or run node-red --help)...

```bash
C:\Users\xxxxx>node-red --help
Node-RED v2.0.5
Usage: node-red [-v] [-?] [--settings settings.js] [--userDir DIR]
                [--port PORT] [--title TITLE] [--safe] [flows.json]
       node-red admin <command> [args] [-?] [--userDir DIR] [--json]

Options:
  -p, --port PORT port to listen on
  -s, --settings FILE use specified settings file
      --title TITLE process window title
  -u, --userDir DIR use specified user directory
  -v, --verbose enable verbose output
      --safe enable safe mode
  -D, --define X=Y overwrite value in settings file
  -?, --help show this help
  admin <command> run an admin command

Documentation can be found at http://nodered.org

```

e.g. set your service to run `node-red -u C:\Users\jon\.node-red`

---

<div class="post-metadata">

**Author:** ![Yonny24](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/yonny24/32/49675_2.png) [@Yonny24](https://discourse.nodered.org/u/Yonny24)\
**Post date:** [21 October 2021 20:29 UTC](https://discourse.nodered.org/t/adminauth-not-working-windows-10/52521/3 "2021-10-21T20:29:25Z")

</div>

Thank you so much. That did it. Created a new user with admin rights. Logged in, started up the service with those credentials of the new user and it created the .node-red repos/folders etc .

But had to reconfigure a lot of the nodes/flows as they did not import properly from the json dump.  
Well, I have the other under the local account also that I can swap back if needed.

---

<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:** [21 October 2021 20:30 UTC](https://discourse.nodered.org/t/adminauth-not-working-windows-10/52521/4 "2021-10-21T20:30:27Z")

</div>

you can run both at the same time if you need to - just set a different port number using the `-p` command line arg.

---

<div class="post-metadata">

**Author:** ![Yonny24](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/yonny24/32/49675_2.png) [@Yonny24](https://discourse.nodered.org/u/Yonny24)\
**Post date:** [21 October 2021 20:45 UTC](https://discourse.nodered.org/t/adminauth-not-working-windows-10/52521/5 "2021-10-21T20:45:21Z")

</div>

exactly what I have done just before I saw your answer. set up a new service also.  
😃

---

<div class="post-metadata">

**Author:** ![Yonny24](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/yonny24/32/49675_2.png) [@Yonny24](https://discourse.nodered.org/u/Yonny24)\
**Post date:** [21 October 2021 20:52 UTC](https://discourse.nodered.org/t/adminauth-not-working-windows-10/52521/6 "2021-10-21T20:52:56Z")

</div>

The only conflict I had was the same telegram bot running - so lots of warning errors.

Easy enough to create another bot.

---

<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:** [4 November 2021 20:53 UTC](https://discourse.nodered.org/t/adminauth-not-working-windows-10/52521/7 "2021-11-04T20:53:15Z")

</div>

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