A couple of hours ago I was talking about my past and current projects with someone and they mentioned that Hipstervision was down. Returning a nasty 403 error.
What the hell?
I know I've left that site fall by the wayside lately as I was focusing on other things, but it should nevertheless at least respond with something when you try visiting it.
Nginx was running. Node.js processes were running as well. And yet, the 403 error persisted.
Restarted everything. Went through all the relevant configurations and still .. nothing. Everything checks out. It makes absolutely no sense for the damn site to be returning a 403.
So I try some other sites running on the same server. All but one return a 403.
Whaaat? O.o
And then I tried a particular document from the working site, on a different domain. It worked. Served the document flawlessly.
But ... dear Nginx, I'm using server_name things, you were supposed to treat each domain as a somewhat different server and respond accordingly. I mean, come on, this is technology from the late 1990's when people realized it might be useful to have more than one website per server.
Turns out in all config files I had this:
server {
listen 80;
server_name hipstervision.org;
But on that particular site I had:
server {
listen my-ip:80;
server_name something.something;
Not sure why that was the case, but apparently Nginx pushes all requests to the most specific listen rule first and only worries about domains and server names later.
Good to know!
Continue reading about Quick and easy way to getting burned by nginx
Semantically similar articles hand-picked by GPT-4
- Switching from apache to nginx is a dream
- Being hacked killed a 6k traffic spike on my blog yesterday
- You are allowed to invent HTTP status codes
- Remember to feed your sysadmins
- A lesson about client-side templating
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️