Hi, I am wondering if there is a way to get rid of this message and the subsequent scrolls and clicks required to eventually access Node-red ? I know it’s not strictly a Victron issue but as in my case Node-red is part of Venus Large and hosted on the cerbo, I’m hoping someone here has a solution.…

It’s not really clear what you want. Do you have a Node-Red dashboard you want to stay connected with? Which IP address are you using? Local or the internet address?

I am using the IP of the Cerbo on local network, plus port, 192.168.1.41:1881. I basically want Node-red to be accessible on my local network without any security warnings or scrolls or additional clicks required, i.e. I type in the IP address/port number and it opens the page, as simple as that. I…

The issue is that modern browsers do not trust self signed certificates, nor https connections when connecting via any other address than what the CA issued it too (e.g. C-NAME or IP). When you connect via VRM’s proxy, all certificates check out. You can probably fix it by standing up a reverse p…

If you use Firefox and go to the local IP, once you set a security exception you shouldn’t see the warning any more.

@Diederik I have a screen in my kitchen which is often restarted while I do various things and each time I need to re-do the security thing to reopen Node-red. @deon.korb All those suggestions seem above my pay-grade. Is it possible to get a certificate from Victron ? Is it possible to access No…

My guess it that Victron will not address this. They officially support secure access via VRM and if you want local, you must do it yourself. Understandable. You might be able to access it on http if you set your GX security to unsecured (with all the expected drawbacks…): [image] I am not sure. …

Yes I would happily use the VRM route but it doesn’t stay connected for very long any more which means I still end up wasting time, but that explains why they aren’t going to give out a certificate. Looking at the settings menu on my cerbo I don’t have the same options. Maybe I need to update Venus…

*Thanks but I get “refused to connect” if I use port 1880.

This has nothing to do with Node-Red I guess.

Get rid of "Your connection is not private" timewaste when opening node-red

Node-RED

Diederik (Diederik) 8 September 2025 12:15 8

I looked it up for you. You can run node-red on port 1880 http. There is quite some info about this.

Topic		Replies	Views
Issues connecting to node-RED, take 2 Node-RED parallel , ess , vrm , bug_report , cerbo-gx	8	203	31 January 2026
Direct link to NodeRed dashboard Node-RED vrm , node-red	9	769	9 October 2025
Keine Verbindung zu Node Red aus VRM Portal Deutschsprachiger Bereich vrm , node-red , cerbo-gx	1	226	27 March 2026
Hilfe NodeRed lässt sich nicht öffnen Deutschsprachiger Bereich node-red	8	324	3 November 2025
Issues connecting to node-RED or its Dashboard Node-RED vrm , professional , node-red , gx_device , bug_report , cerbo-gx	14	505	27 January 2026

Get rid of "Your connection is not private" timewaste when opening node-red

Related topics