I tried using the Node-RED Projects feature but can't get it working.
specs:
running as docker container:
image: nodered/node-red:latest
with a reverse proxy between, doing the authentication part (if that matters).
Node-RED version: v2.0.6
Node.js version: v14.17.6
git version: 2.24.4
"raw" installation, so no (additional) modules installed
Error message, when I try to create a new project:

I tried multiple git credentials but these are "not working":
also if I generate a ssh-key it didn't work.
And I can say, my docker image is up to date, as the output of the following command is the below:
docker image pull nodered/node-red:latest
latest: Pulling from nodered/node-red
Digest: sha256:ddd05759e91dce9db82d36a3df66011936cc49d59ac329589df379c44e74867e
Status: Image is up to date for nodered/node-red:latest
docker.io/nodered/node-red:latest
If you have any ideas or need some informations, don't hesitate to write to me.
Thank you.
As I tried a third time, I updated the image to the new node-red version 2.1.
While updating I thought, maybe the settings could differ so I let it create default settings.js which brought the projects working. So there is definitely a error in my configuration, so I'd thought of sharing it here.
difference to default settings.js:
- as described in docs, to make it read the env var for credential secret
module.exports = {
credentialSecret: process.env.NODE_RED_CREDENTIAL_SECRET,
//...}
2. I disabled auth beucase I use another authentication mecanism. (this was the problem!
)
adminAuth: {
type: "credentials",
default: {
permissions: "*"
}
},
- editor theme
midnight-red 4. codeEditor lib monaco and 5. theme tomorrow-night
editorTheme: {
theme: "midnight-red",
projects: {
enabled: true,
/* true or false no difference here, because I set it over environment variable */
workflow: {
mode: "manual"
}
},
codeEditor: {
lib: "monaco"
options: {
theme: "tomorrow-night",
}
}
},
- If I only have 1 and 3 (only
theme) projects work.
- (it looks to me as) 2 is the problem, also somehow not even neccecary anymore in this new version (2.1)
I still don't know why, but the problem occurs definitely when disabling auth with following settings.js:
module.exports = {
adminAuth: {
type: "credentials",
default: {
permissions: "*"
}
},
}
So if you run into the same problem, you might be fine by just removing/commenting out that part of settings.js.