Whenever my Windows machine is restarted (which happens often due to Windows updates), much of the time my node fails to start automatically. Looking in the logs, the last entry I see in these situations is: “Invalid configuration: invalid contact.external-address: lookup “[my-ddns-hostname]” failed…

Please, start a cmd.exe with Administrators rights and execute the command from this post: [image] After restarting my server today I cant get up my node again troubleshooting Regarding the temporary DNS issues after system reboot, it is very likely that the storagenode se…

Thanks for the link to the other post. This will help mitigate the problem, but its not a permanent solution. There will be times when the DNS service has started, yet the node is still offline.

If you did this dependency and still have a problems - let us know, thank you!

This is still a problem after making that dependency. My computer restarted while my internet was intermittently down, and the storagenode never started.

What the reason in the logs and system events?

I thought I had replied to your question, but I guess not. Anyway, I just ran into this again and the errors are below. I censored my dynamic dns hostname. 2020-06-08T04:11:59.970-0700 ERROR Invalid configuration. {"error": "invalid contact.external-address: lookup \"XXXXXXXXX.dynamic-dns.net…

In your specific case I would like to recommend to add automatic restart for the storagenode service via Services applet.

Storj Community Forum (official)

Node fails to start due to race condition / no internet

Node Operators troubleshooting