How to troubleshoot offline node

[Alexey]

@arrogantrabbit

Turn off windows firewall temporarily (or permanently – it’s dubious value proposition for a machine that is in the private lan) to rule out you adding rules in the wrong zone.

@ronydeolindo
Please, don’t. The installer may refuse to install the service, the Windows firewall is in its dependencies. It’s better to create inbound rules instead

@arrogantrabbit

confirm that your noIP address is the same that is on the WAN interface of your router, and that node external address matches, and that it resolves to that external IP. You may not have a public address. Plex does nat traversal.

nslookup your.noip.domain 8.8.8.8

The returned IP must match your WAN IP and IP from yougetsignal. If it’s not match, you need to check your DDNS updater. It’s better to configure it on your router (usually in the DDNS section).
However, if your WAN IP doesn’t match IP on yougetsignal, then you do not have a public IP and need to contact your ISP and ask them to switch your connection out of CGNAT to get a public IP, it can be dynamic, but must be public (the WAN IP will match the IP on yougetsignal).

@arrogantrabbit

What is in the node’s log?

How do I check my logs? - Storj Docs

Please also make sure that you provided your external address with port in the contact.external-address: option of your config.yaml file