Cant set auth for Node-red at Render

General
1

Hello everyone, im trying to deploy Node-red on render.com at free instance as web service, using as source github repository (GitHub - yarickshark/Node-red), but i cant set authorization. I just uncommented part of "settings.js" - adminAuth.
Deployed same files locally on pc with windows - everything work as it should (authorization works). When i do the same deploying at render - there is no authorization, just node-red web.
How to make authorization work?

node-red version 4.0.9

2

Are you able to see the node red startup log?

3

Your repo only contains the userDir folder. How have you installed Node-RED itself? And how do you run it?

4

Installed node.js, installed node-red on pc (C:...), started, set auth.
Copied to D:..., made a local repo from copy, pushed to github. At render set repo to use for deploy, and its live, but without auth

5

Yes, here logs from render:

Logs 
12 Apr 20:02:23 - [info] Stopped flows

Apr 12 11:03:33 PM12 Apr 20:03:33 - [info] Linux 6.8.0-1024-aws x64 LE

Apr 12 11:03:34 PM12 Apr 20:03:34 - [info] Loading palette nodes

Apr 12 11:03:38 PM12 Apr 20:03:38 - [info] Settings file : /opt/render/.node-red/settings.js

Apr 12 11:03:38 PM12 Apr 20:03:38 - [info] Context store : 'default' [module=memory]

Apr 12 11:03:38 PM12 Apr 20:03:38 - [info] User directory : /opt/render/.node-red

Apr 12 11:03:38 PM12 Apr 20:03:38 - [warn] Projects disabled : editorTheme.projects.enabled=false

Apr 12 11:03:38 PM12 Apr 20:03:38 - [info] Flows file : /opt/render/project/src/flows.json

Apr 12 11:03:38 PM12 Apr 20:03:38 - [warn]

Apr 12 11:03:38 PM

Apr 12 11:03:38 PM---------------------------------------------------------------------

Apr 12 11:03:38 PMYour flow credentials file is encrypted using a system-generated key.

Apr 12 11:03:38 PM

Apr 12 11:03:38 PMIf the system-generated key is lost for any reason, your credentials

Apr 12 11:03:38 PMfile will not be recoverable, you will have to delete it and re-enter

Apr 12 11:03:38 PMyour credentials.

Apr 12 11:03:38 PM

Apr 12 11:03:38 PMYou should set your own key using the 'credentialSecret' option in

Apr 12 11:03:38 PMyour settings file. Node-RED will then re-encrypt your credentials

Apr 12 11:03:38 PMfile using your chosen key the next time you deploy a change.

Apr 12 11:03:38 PM---------------------------------------------------------------------

Apr 12 11:03:38 PM

Apr 12 11:03:38 PM12 Apr 20:03:38 - [info] Server now running at http://127.0.0.1:10000/

Apr 12 11:03:38 PM12 Apr 20:03:38 - [warn] Encrypted credentials not found

Apr 12 11:03:38 PM12 Apr 20:03:38 - [info] Starting flows

Apr 12 11:03:38 PM12 Apr 20:03:38 - [info] Started flows
6

Why is the settings file it is using not in the same folder as the flows file?

7

Is it should be? its installed on pc with windows that way...

Can it be that i installed node-red on windows pc, copied to repo, but render servers probably using linux?

8

On a normal install on Windows or on Linux they would both be in the user's .node-red folder. Also they are in the same folder in your github repo.

Which settings.js did you edit and have you checked that the one it is actually using has your edits in it?

9

Maybe i dont understand a question

I edited setings.js in browser in repo (that one, which not at folder, at pc it must be in .node-red folder), and than rebuint it at render (that must reload all files before deploy)

10

I meant that you should look at the file /opt/render/.node-red/settings.js when node-red has started and check that it contains the admin auth changes.

11

If you look on GitHub under my id, you will find an alternate installer for Node-RED that will do what you need. You don't have to run it if you don't want to but you can borrow the process and adapt for your own needs.

Instead of the "normal" install of Node-RED - which installs to a global location, you install it to a local folder and create a userDir folder inside that (userDir is where the settings and flows all go). That way, you have everything in a single parent folder.

You create a script entry in the parent package.json file so that npm start will run Node-RED directly which matches the instructions for running custom node.js apps from the render.com docs. You can use this as your start script (assumes that userDir will be in the data sub-folder, adjust as needed:

node node_modules/node-red/red.js --userDir ./data