Node offline last night

[Alexey]

Not the year-old version, but exactly 2.1.0.5, if it’s a root cause and not some firewall or port forward misconfiguration.

If your node is online, then you may try to fix a QUIC issue, but if it’s offline, then you need to fix this first.

I would like to suggest to check everything from this checklist:

My Node is OFFLINE for 2 hours

It should connect in seconds. There are a few things you should check. Start with checking the port. On https://www.yougetsignal.com/tools/open-ports/?port=28967 you can fill in the domain or IP you are using in the run command. Then check the port. If it’s closed, it could still be several things. Make sure the WAN IP you see in your router settings matches the IP shown on the above page. Make sure your port forward is set up correctly. That means no filter on incoming IPs, forwarding to th…

Especially that your ADDRESS option contains either updated public IP (you may see it on yougetsignal) or updated DDNS hostname.
if you use a DDNS hostname, make sure that it resolves to the same public IP as on yougetsignal and it’s match the WAN IP on your router:

nslookup your.ddns.hostname 8.8.8.8

should return the same IP as on yougetsignal and matches your WAN IP.