DNS failure (user caused)

Node Operators troubleshooting
1

I let my DNS conf lapse with ddns. I fixed it but I’m still showing no ingress. Any suggestions on how to get it back to good? Thanks

2
  1. confirm you actually fixed it.
  2. Depending on how long it was offline you may or may not recover, and in you do – ingress may take a long time to pick up.
  3. The satellite would throttle requests from your node after few unsuccessful attempts. Shut down node for some time, then start it again.
2 Likes
3

Hello @zomgreg,
Welcome to the forum!

You also need to check, that you actually still have a public IP: compare the WAN IP on your router with the IP there: Open Port Check Tool - Test Port Forwarding on Your Router

4

I’ve confirmed with telnet that I can reach the domain on the port. I’ll hold and wait to see what happens. Thank you for this input.

5

This is not the same. Please turn off WiFi on your phone and open your domain with port in the mobile browser.
You should get the response, then your port is configured and forwarded correctly.
I.e. http://my.host.tld:28967 should show something like that:

{
  "Statuses": null,
  "Help": "To access Storagenode services, please use DRPC protocol!",
  "AllHealthy": true
}

Also, make sure that the node version is not older than a minimum version on https://version.storj.io/

1 Like
6

Thank you for this. I didn’t know about this method for checking health.

Looks like things are happy. And it looks like ingress is back as well. Good answers, Storj bros. Thank you.

storj
storj842×167 11.3 KB

1 Like
7

You can go a step further and setup remote monitoring solution somewhere outside your network to check for that value and notify you if anything changes or node is inaccessible.

example for Uptime Kuma

image
image1290×2796 293 KB

1 Like
8

@arrogantrabbit that’s how I got in trouble in the first place. LOL. I was using DynDNS and was just doing the manual update plan each month since the storj payments don’t even cover the cheap plan. Then decided to stop being a cheapskate and just pay and move on with life, not knowing I had config work to do. Sigh. It’s all fixed now. You guys are great for taking the time to help me unfsck my own mistake. Thanks

9

You mean DDNs plan? I would never pay for DDNS. It makes no sense to pay a monthly fee for the service most providers offer for free. For example, if you host your domain at CloudFlare (you presumably already have your own domain, or if not, you can get one at $5-$10/year, if for no other reason than to have your own provider-independent permanent email address), they offer free access to an API to edit DNS configuration, that can be used by tools like Inadyn to update your external IP automatically inadyn/examples/cloudflare-ipv4-only.conf at d809e2b4f80027d4b9fcf528e06dab844a90b6da · troglobit/inadyn · GitHub. (They offer a lot of free stuff, like caching, zero trust, email forwarder, warp, etc.— so that $10/year is pretty much noise). And from personal experience, I’m yet to have had an issue with their DNS.