-
Notifications
You must be signed in to change notification settings - Fork 72
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
getaddrinfo ENOTFOUND #69
Comments
Not sure what is going wrong there. Maybe its a system bug like here: nodejs/node#5436. Anyways the errors are only about the Websocket/Event system. Does it work if you turn off events in the account node configuration? |
No, the errors remain the same. I deleted all docker images and pulled node-red:latest again. I tried to set 8.8.8.8 as DNS in the container with no success. |
Finally: trailing whitespace within page configuration... secondsWaisted.forEach(() => head.desk()) Feature Request: Please trim whitespace... :) Anyway... thank you for the great node! Henning |
Hi,
if i configure a file for the cookie the next time i do a full deploy i get this error:
The next time i restart node red i get the same error but node red refuses to start
If i ping the address i get answers:
If i delete the file configuration everything works fine but i have to log in every time i do a full deploy.
I am running node-red-docker:latest on ubuntu 18.04 with alexa-remote2 3.4.1
Do you have any ideas whats wrong?
Henning
The text was updated successfully, but these errors were encountered: