SSL certificates still needed for NodeRed?

Third party integrations Node-RED
1

Wondering if anyone else has experienced this. I moved to Nabu Casa from DuckDNS and a port being forwarded for remote access to HA. Now I don’t see the need for the Let’s Encrypt SSL certificates so I removed the HTTP code from my configuration.yaml file. This is when I noticed that NodeRed and Grafana give me a 401: Unauthorized error when trying to use the Supervisor web UI. Yes I configured SSL to false for NodeRed but the certfile and keyfile entries appear to still be needed there.

2

I do not use SSL for my Node-Red, but the certfile: and keyfile: entries are still present in the configuration.

3

Your going to the http pages not https? I have the files commented out in config.yaml but the addons still have the file names. Have you tried direct access? Your ha ip + :1880 instead of 8123. Also it wouldn’t hurt to go to the supervisor, system page and reboot the host.

4

I works directly to port 1880 which is good. It just seems odd why it gives the 404 error through the web UI. Host has been rebooted, so there must be another setting persisting.

5

Is it your long-lived token that is the issue?

6

Have you cleared the browser cache?

7

The keys in the config for the SSL stuff are still needed yes, but they can be empty, they don’t have to be pointing to the actual files, not when SSL is set to false.

8

Cleared browser cache, yes. no change. I can create long-lived access tokens, but do not understand where to install them.

certfile: fullchain.pem
credential_secret: *********
http_node:
  password: ********
  username: ********
http_static:
  password: ********
  username: ********
init_commands: []
keyfile: privkey.pem
npm_packages: []
ssl: false
system_packages: []
theme: default
9

No idea if this helps, but if you goto Configuration → Integrations and click on the 3 dots in the Node-Red box, then you have an option to reload the integration.
Under system options you also have an update function that you can try and click.

10

You only need one if you do not use the addon. Look in the log after you try to open the page, The addon has a log page. On the supervisor–>system tab look at the core and supervisor logs for errors.

If there are none you could try turning up the logging in config.yaml

logger:
  default: info
  logs:
    custom_components.nodered: debug
11

Thanks for the idea. I was watching the logs, but now I see this in the supervisor log and not sure what it means. I get the last log each time I try the web UI.

21-12-10 08:38:04 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-12-10 08:38:04 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
21-12-10 08:39:06 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
12

This is usually caused by going to nodered from a history link. Have you tried a different browser or a mobile device?

13

try:

certfile: ''
credential_secret: *********
http_node:
  password: ********
  username: ********
http_static:
  password: ********
  username: ********
init_commands: []
keyfile: ''
npm_packages: []
ssl: false
system_packages: []
theme: default
14

Still receiving the 404 error. I have resigned my self to keep SSL certificates on my internal network.

15

I came across this tip today for getting around the ssl req for esphome. In a chromium based browser you can set a flag unsafely-treat-insecure-origin-as-secure for nodered’s ip address. perhaps it will work with nodered too.

16

Just getting back to this. This is making sense but I still can’t get Chrome to work, but Edge does. It is looking like a security setting in Chrome.