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

[error] Error: getaddrinfo ENOTFOUND #69

Open
Comawhite54 opened this issue Dec 23, 2023 · 1 comment
Open

[error] Error: getaddrinfo ENOTFOUND #69

Comawhite54 opened this issue Dec 23, 2023 · 1 comment

Comments

@Comawhite54
Copy link

Comawhite54 commented Dec 23, 2023

Describe the bug
With the beta 3.x version, I cannot start node red anymore.
It was woking fine with this version.

The crash occur only when I try to access node-red flows for edition.

The crash is caused by :

23 Dec 19:27:16 - [red] Uncaught Exception:
23 Dec 19:27:16 - [error] Error: getaddrinfo ENOTFOUND gateway---****.local
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26)

Setup :

  • Version of node-red : 3.1.3
  • Version of node-red-contrib-tahoma: 3.0.0 - beta 5
  • Version of node.js : 21.4.0
  • Where is node-red installed : Windows 10
  • How is node-red installed : npm
@Murmelspieler
Copy link

Hi, I had the same problem.

The solution was as follows.
In the TaHoma Node in node red. there is a line where the compounding is entered.
image

The input looks like this by default:
https://gateway-1234-1234-1234.local:8443

I have made this change:
https://192.168.178.XXX:8443
Here you have to look at the Fritzbox to see which IP your TaHoma Box has. I have also activated the function that the Fritzbox always assigns the same IP

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

No branches or pull requests

2 participants