Swizec Teller - a geek with a hatswizec.com

    Quick and easy way to getting burned by nginx

    HTTP 403: Forbidden

    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!

    Enhanced by Zemanta

    Did you enjoy this article?

    Published on October 5th, 2011 in Linux, Nginx, Server, Uncategorized

    Learned something new?
    Want to become an expert?

    Here's how it works 👇

    Leave your email and I'll send you thoughtfully written emails every week about React, JavaScript, and your career. Lessons learned over 20 years in the industry working with companies ranging from tiny startups to Fortune5 behemoths.

    Join Swizec's Newsletter

    And get thoughtful letters 💌 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. 👌"

    ~ Ashish Kumar

    Join over 14,000 engineers just like you already improving their careers with my letters, workshops, courses, and talks. ✌️

    Have a burning question that you think I can answer? I don't have all of the answers, but I have some! Hit me up on twitter or book a 30min ama for in-depth help.

    Ready to Stop copy pasting D3 examples and create data visualizations of your own?  Learn how to build scalable dataviz components your whole team can understand with React for Data Visualization

    Curious about Serverless and the modern backend? Check out Serverless Handbook, modern backend for the frontend engineer.

    Ready to learn how it all fits together and build a modern webapp from scratch? Learn how to launch a webapp and make your first 💰 on the side with ServerlessReact.Dev

    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 ❤️

    Created by Swizec with ❤️