Anything will do… See it as an password that keeps your passwords safe. The longer the better (as with password). Make sure to store it somewhere safe.
Ok. Done. I had to be quite patient waiting for it to start, but now the web ui is up, and I’m beginning my exploration!
1 Like
@dickcollier if you take a look at this forum you would find that @frenck spends as much time as anyone answering question and trying to make all of the addons work.
The ones that work to develop HASSIO, HASSOS, and Home Assistant are not paid by the users of HA. They have made an incredible number of changes and improvements since I started using HA. Adding changes and components almost weekly.
Looking at the forum I see a lot of questions asked over and over again (the brand new users I maybe can understand, they don’t know where to find information), but others who have been around just ask instead of looking into the documentation, the cookbooks or Youtube.
I am not a programmer, but I do try to help others if I can. Nothing keeps people from helping out others more than when the ones asking questions are rude or over-demanding.
2 Likes
this is my case. Newb here … I think is just
“ssl”: false,
in nodered configuration, instead of true, but I might be wrong: nevertheless my node-red is fully working locally. When abroad I use VPN to connect home. I do use NGINX though, which was a pain to install, but now works
p.s. I share the frustration, one of the most complicated things (fore me at least), is the handling of SSL certificates, letencrypt and all the jargon related, that I never understood well, so I went the route of having all locally
That is correct @Klagio. In a closed network, there is nothing wrong with that (although even on internal network I personally still use SSL). The addon is preconfigured in the most secure matter. Reasoning: one should do effort to lower security, not the other way around.
PI3B+, HA 0.77.2. Changed config to ssl false.
NodeRed configuration file:
{
"log_level": "info",
"credential_secret": "",
"users": [
{
"username": "",
"password": "",
"permissions": "*"
}
],
"http_node": {
"username": "",
"password": ""
},
"http_static": {
"username": "",
"password": ""
},
"port": 1880,
"ssl": false,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"require_ssl": true,
"system_packages": [],
"npm_packages": [],
"init_commands": []
}
Log file:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Hass.io Add-on: Node-RED v0.6.1
Flow-based programming for the Internet of Things
From: Community Hass.io Add-ons
By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
armhf / HassOS 1.10 / HA 0.77.2 / SU 128 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing...
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing...
FATAL: Setting a credential_secret is REQUIRED!
[cont-init.d] 10-requirements.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
-----------------------------------------------------------
Oops! Something went wrong.
We are so sorry, but something went terribly wrong when
starting or running this add-on.
Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.So I change ssl to false, log says a credential_secret is required.
I put in a really long and compliant credential, log says I need a user name.
I put in a user name and password, logs says my password doesn’t pass pwnd test.
I don’t care. This is on my HOME lan. I’m NOT going to change my login password just to run NodeRed. This is ridiculous.
-
credential secret is required by node red.
-
ssl true can be set to false.
-
you can disable the check against your commonly used password, and you can use it for each of the user/pass entries in the options. Right here in the docs: https://github.com/hassio-addons/addon-node-red#option-i_like_to_be_pwned
-
The user/pass you choose for these server-type-addons are independent of your home assistant password. While they CAN be the same as your HA password, they do not need to be the same.
The users who “don’t care” about any of this are no longer the default users, and need to expend a little effort to prove it. This is just how it is.
I DID set ssl to false. It didn’t listen. At least the uninstall went smoothly.
The majority of the community ssh addons are going to have a similar procedure. Even the ones that do not yet check against the breached password database will be updated eventually (if there are any left). So your frustration is only going to cut you off from most of the other offerings.
Your attitude stinks towards people that are trying to make things better @cogneato and @frenck do a fantastic job
5 Likes
hmm no answer … I hope you thought about your comments and if you did Thanks
Bye Falicia
Put something in all username and password field
I’ve upgraded this morning to ha 0.77.3 and node-red 0.6.1, since then I cannot get communication working between Node-Red and HA. I have the error message:
4 Sep 15:18:31 - [error] [server:Home Assistant (http://hassio/homeassistant)] Home assistant connection failed with error: Connection to home assistant could not be established with config: http://hassio/homeassistant <password redacted>
I’ve configured the password of my api config in HA. In HA in the system logs I see the error message (already for a longer time):
WARNING (MainThread) [hassio.api.proxy] Unknown HomeAssistant API access!
Is someone else having problems with node-red not registering state changes?
I have a flow that sets the TV volume depending on the source. But the last days it wasnt working.
Today i inserted a debug node and after deploying it was working again ???
Also, is there anything i need to pay attention to when updating to 0.77 with the new auth system?
Adding the following to the NodeRed container makes the use of Projects in Node-Red possible
“system_packages”: [
“git”,
“openssh-client”,
“openssh-keygen”
],
With this I could generate a new SSH key-pair from the Node-Red UI.
I still had problems setting the remote so ended up using a console in the container and setting the remote, this may be due to needing to add the git server to the known hosts.
git push --set-upstream origin master
This configuration has survived a restart, so Projects with the git support looks to be working.
I’m suddenly suffering the " [error] [server:Home Assistant] Home assistant connection failed with error: Connection to home assistant could not be established with config: http://hassio/homeassistant <password redacted>"
In hassio logs I see this:
WARNING (MainThread) [hassio.api.proxy] Unknown HomeAssistant API access!
It has been working fine on HA v0.77.3 until this afternoon.
Have tried restarting, changing the api key to have a new one on next restart, but no luck. Any ideas of what’s happening?
Like wise. Was working ok until this afternoon, now seeing the same errors as foraster in NodeRed addon and Hassio logs
I have temporary solved this changing the configuration node:
from http://hassio/homeassistant + API key
to https://my.domain.com + legacy HA password
Not my preferred solution anyway
Would be interesting to know what has happened with the auth failure in hassio