Well, it happened again. I broke my server.
On Friday afternoon, I was working on someone’s site that is hosted on my server. I had PuTTY and WinSCP opened while I was working.
I remember months ago typing in “whereami” and found out that it’s a real package. At first instinct, I thought it was a command to state what directory you are in. So I decided to install it.
That was the mistake, installing whereami.
The install stopped at about 78% on my screen, and froze. All of sudden WinSCP disconnected but my SSH session was still up at the frozen install. At first, I thought that me indexing a folder killed it.
Luckily, my server is hosted via DigitalOcean. They have a nice little console window that works no matter what. Thank God.
After many hours that night figuring out what the fuck I did, I went to bed in defeat. I worked all that weekend so I had no time to investigate. I decided to create a support ticket to see what they can do since I had no idea.
They told me hours later to run some commands to make sure my network config is correct, and it was from what I could tell. The main issue at that point were a couple of things:
- All outbound traffic times out while trying to connect
- Anything trying to connect outside the server fails
- Since nothing could connect, nameservers died
So I investigated more on Sunday night and found a major issue with my config. The default gateway was set to 0.0.0.0! Ha! I found the issue!
I quickly set the gateway back to what it should be, and heaven’s light shined on me. All was working!
So RIP to the 5 websites and 1 Twitch bot that are all hosted on this server.
Turns out whereami is some networking setup package? I still don’t really know but it reset my entire network config.