Closed Schmandre closed 3 months ago
Hi @Schmandre!
The EAI_AGAIN error typically indicates a DNS lookup timeout, which often points to network connectivity or proxy-related issues. Given that you're encountering this error for domains unrelated to VSH, it suggests there might be a broader issue with your setup.
Additionally, I'd like to note that the information about the PRO plan is sourced from MQTT messages originating from the VSH backend, utilizing a different port and protocol than the version check, which operates over HTTP. Perhaps this information might be helpful for troubleshooting.
Thank you for the hint. Was a local problem indeed 👍🏽☺️
PiHole stopped working „well“ and interrupted everything.
It’s working again.
Hello,
since today I have the problem, that inside the nodes there is a message "version check failed". If I try to use a voice command, Ill get the error message, that the device is offline.
If I check my subscription, I can see that the connections is on "PRO-Plan" so there must be a working connection to check that.
Log shows
A small edit. Is just tried a fresh docker install of node red and tried to install v 4.2 directly. I got the error, that the URL
https://registry.npmjs.org/node-red-contrib-virtual-smart-home failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org
is not reachable.If I ping it from docker host, working. If I try to open inside network, working. Any ideas how to fix?