Having problems with no less than three of my instances this morning -- can't get through at all. (Fortunately, the TootCat server seems to be ok.)

Anyone else having DigOc issues?

@dredmorbius I'm not sure. They offer CDN as an option, but I haven't used that for any of my servers.

@dredmorbius The status page says everything is fine... but perhaps the CF outage is causing connection problems between me and DigOc.

@dredmorbius Looks to be a networking issue. If I ssh into TootCat's server, I can then contact the others by ssh.

@woozle Smells like DNS or routing.

Do the other hosts resolve?

@dredmorbius addresses resolve correctly, but neither ssh nor https can get through.

I'm on chat-hold with Spectrum about it (after first rebooting the modem, just in case). "We are currently experiencing higher than usual wait times." -- which may indicate some kind of outage that they're working on, or may just be a way to get people to not complain about their inadequate staffing.

Follow

@woozle Network troubleshooting. If any step fails, that's where to start digging further:

  1. Confirm local and local ISP connectivity. ping www.google.com usually establishes this. If not, local host/router/ISP issues.
  2. Resolve remote host: dig <hostname> If not: DNS issues.
  3. Test connectivity: ping <hostname or IP> If not; connectivity.
  4. Check routing: mtr <hostname or IP> Especially watch for latency, dropped packets (loss), or failure to rech remote, or rapidly changing routing (different intermediary hosts).
  5. Protocol-based connections. Tools like ssh w/ verbose options enabled (1--4 -v arguments), or HEAD, curl -h or wget should be useful here, other services as appropiate. Is the server up and responding? Success or error codes?
  6. Reverse-path routing, local or remote firewall: If you can get on the box by other means, see what connection attempts look like from its side. Errors?
  7. Check egress route. I've seen boxes which could receive but not send remote traffic due to colo routing fuckups. Try pinging / mtr to your local internet gateway public IP.

If all this works but you still have issues, dig further.

@dredmorbius

I was farmiliar with (and did) steps 1-3; hadn't heard of mtr before; I always just used traceroute -- but I didn't think to try it this time (I think Frontier used to make it useless, somehow, so I got out of the habit) and hey, mtr looks seriously nifty. I've saved that and a link to your list for future reference.

@woozle Neat feature of mtr is that you can toggle display of ASN rather than IP, which helps when BGP is melting down.

Sign in to participate in the conversation
Toot.Cat

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!