20

Holy FREAKING shit!! This was worst stupidest mistake I have ever made!

About 9 hours ago, i decided to implement brotli compression in my server.

It looked a bit challenging for me, because the all the guides involved compiling and building the nginx with brotli module and I was not that confident doing that on live site.

By the end of the guide, the site was not reachable anymore. I panicked.

Even the error logs and access logs were not picking up anything.

About a dozens guides and a new server and figuring out few major undocumented errors later, it turns out the main nginx.conf file had a line that was looking for *.conf files in the sites-enabled directory.

But my conf file was named after the domain name and ending with .com and hence were not picked up by the new nginx.conf

I'm not sure if I wasted my 9 hours because of that single line or not. But man, this was a really rough day!

Comments
  • 7
    This was a good learning opportunity bro. Nothing more. This could have happened to the best of the best, and i for one thank you for sharing this here so we may take note.
  • 4
    I read somewhere something like: "every developer has a testing environment. The lucky ones even have one seperated from their prod environment..."
  • 0
    @Wack that is gold
Add Comment