adminAuth not working windows 10

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.
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.

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?


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)...

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]

  -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

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

1 Like

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.

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

1 Like

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

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

Easy enough to create another bot.

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