Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Self-Signed Certificate of the Huebridge (rectangle) Error message #436

Open
rsch90 opened this issue Jun 25, 2023 · 1 comment
Open

Self-Signed Certificate of the Huebridge (rectangle) Error message #436

rsch90 opened this issue Jun 25, 2023 · 1 comment
Labels

Comments

@rsch90
Copy link

rsch90 commented Jun 25, 2023

Describe the bug
A clear and concise description of what the bug is.
I am using the rectangle Bridge and since a couple of days I see the following entries in the Node-Red Log:

25 Jun 14:20:36 - [info] [hue-bridge:Huebridge] Initializing the bridge (192.168.50.53)…
25 Jun 14:20:37 - [info] [hue-bridge:Huebridge] Error: self signed certificate

This leads to the Node does not work as desired. It only shows "connecting..." nothing more. I had this running earlier. But something broke this.

Flow to Reproduce

[
    {
        "id": "de63398919a2eaab",
        "type": "hue-bridge-node",
        "z": "abd3699b43c72ae4",
        "name": "",
        "bridge": "bc8d4785237d1937",
        "autoupdates": true,
        "skipglobalevents": false,
        "initevents": false,
        "x": 1130,
        "y": 80,
        "wires": [
            []
        ]
    },
    {
        "id": "bc8d4785237d1937",
        "type": "hue-bridge",
        "name": "Huebridge",
        "bridge": "xxx.xxx.xxx.xxx",
        "key": "removed due to security",
        "worker": "10",
        "autoupdates": true,
        "disableupdates": false
    }
]

Expected behavior
At least a switcht to aknowledge Self-Signed and ignore the Certificate error. Or at least switcht to http instead of https. As this is all local this should be fine.

Screenshots
https://imgur.com/a/LdetQRa

Please complete the following information:

  • Node-RED version: 3.0.2
  • NodeJS version: 16.9.1
  • Device running Node-RED: Raspberry
@rsch90 rsch90 added the bug label Jun 25, 2023
@rsch90
Copy link
Author

rsch90 commented Jun 25, 2023

I did some research on my own based on what I found in the Code.
Based on Information from here there are certain Bridges that currently run with a self-signed certificate an others with a valid certificate issued by signify.

You can find my modifications within the attached api.js file.
I added row 5+6
and did changes on row
33 and 67
From my understanding you can provide to the https.Agent a specific CA File to be used for the request. This is what I am doing.
With this modification I was able to use the Node again :)

As I am not an experienced JS developer I leave this to you how to implement it in a proper way to the Node.
api.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant