Spent 3 hours chasing a DNS issue that was just a typo in a config file

Last night I was trying to fix a website that wouldn't load for visitors, and I kept checking firewall rules and router settings. Turns out I had typed 'exmaple.com' instead of 'example.com' in the hosts file. Has anyone else wasted way too long on something this simple?

3 comments

3 Comments

averymartin3d ago

Feel you on this one. I spent a whole evening once trying to fix a login page only to find I had a semicolon in the wrong spot. It's amazing how one tiny mistake can eat up hours.

mary_martin223d ago

Count to three times I've spent way too long staring at code only to realize I was missing a closing bracket. It's like the computer knows exactly where to hide the dumb little things so you feel like a genius when you finally spot it. Honestly, half the time I think my brain just refuses to see the obvious until I've properly punished myself for being so careless. And then you fix it and it works instantly and you feel both relieved and like the biggest idiot on the planet. Classic programming cycle right there.

henderson.oscar3d ago

Idk man, it's like the computer hides those little mistakes on purpose just to humble you. @averymartin I once spent a full afternoon chasing a bug that turned out to be a typo in a comment, not even code.

-1