I get 400 bad request using your addon on the sidebar, “The plain HTTP request was sent to HTTPS port”.
My HASS uses ssl; how do I configure this? I can get in from outside webpage using https://
I am also having the same issue and can access by adding https:// in the url.
An issue here as well, the log says
22-02-02 13:16:15 WARNING (SyncWorker_6) [supervisor.addons.validate] Add-on config ‘auto_uart’ is deprecated, use ‘uart’. Please report this to the maintainer of Node-Red Dashboard
22-02-02 13:16:16 WARNING (SyncWorker_1) [supervisor.addons.validate] Add-on config ‘auto_uart’ is deprecated, use ‘uart’. Please report this to the maintainer of Node-Red Dashboard
@Maran this is not an issue but I fixed it anyways
@djsheetu and @starmanj I just uploaded a new version in which you can configure if you use ssl or not. Can you please try with that? I didn’t test it yet.
For better responsiveness from my end, please open issues in the GitHub repo where I get notifications (for the love of me, I can’t get notifications in this forum)
I did check it again and the uart message does not appear anymore however the if i click on the left for the dashboard it get the 502 gateway message
/a2b947f4_node-red-dashboard"
[04/Feb/2022:13:37:22 +0100] 502 172.30.32.2 192.168.X.XXX, 172.30.32.1(172.30.32.2) GET / HTTP/1.1 backend 172.30.32.1:1880 192.168.X.XXX /
2022/02/04 13:37:23 [error] 355#355: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a2b947f4-node-red-dashboard, request: “GET / HTTP/1.1”, upstream: “http://172.30.32.1:1880/endpoint/ui/”, host: “192.168.X.XXX:8123”, referrer: "http://192.168.X.XXX:8123
@maran are you sure your node red is configured to listen on the 1880 port?
edit:
I just tried to see if we can avoid opening the node red port in order for the addon to work, but sadly that is not possible as the node-red addon restricts the ingress access to the home assistant docker only.
Just released a new version that doesn’t depend on the open port and ssl configuration of node red, it communicates directly with the node red instance on the host network (you don’t need to open node red with a public port).
@maran can you please update and let me know if that works for you?
Node red is working fine the whole day here and if not I would notice it directly.
I updated to dev11 stopped and restart and now working fine.
Thank you for the help, if issues occure I will report this here
1 Like
Is there a way to force the update? I get the same error, but the update is not yet available within home assistant and a restart of supervisor or home assistant does not work.
Yes, go to the addons section, click the addon store, then use the hamburger (3 dots) to open the menu and click the “check for updates” button, you should then see the update available if you go into the add on info page
no updates yet 
Then just delete the addon, delete the repo and add it again
I use the repo for multiple addons so I can’t uninstall it. Reinstallation remains the same version
What addon are you talking about? My dashboard addon lives in a custom repo that doesn’t have any other add-ons
ohhh i’m verry sorry 
i’m using home assistant from Frenck’s repo 
My addon just creates a tab for node red dashboard, you still need the official node red addon to run
Oké 
thanks for your quick reply!
Glad to announce that I just released the first stable release - I added a standard addon CI and improved the docs - https://github.com/regevbr/addon-node-red-dashboard
I was preparing a long post with lots of (hopefully relevant) logfile snippets …but then this morning I get “You have dev10 installed. Click update to update to version 1.0.2”.
When I did the Update I got
Image ghcr.io/regevbr/node-red-dashboard/aarch64:1.0.2 does not exist for addon_a2b947f4_node-red-dashboard
… but after Host Reboot (there have been quite a lot of updates I have applied the last couple of days), it seems to be working well.
thank you ! 
1 Like
Just updated and can confirm works fine now with https://. I just had to uninstall and reinstall the add-on.
Thanks heaps!
1 Like