Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

this is my first web app deployment and am running into all sorts of issues.

I am currently going for a nginx + gunicorn implementation for the Django app, but mostly this question relates to nginx configurations. For some context - nginx would receive connections and proxy to the gunicorn local server.

in the nginx configurations, where it says server_name do I have to provide one? I don't plan to use domain names of any kind, just through my network's external ip (it is static) and the port number to listen to.

My desire is that when I access something like I would be able to get the site.

The following is the sample code that I will base the configurations on for reference.

   server {
        listen   80;
        server_name WHAT TO PUT HERE?;

    root /path/to/test/hello;

    location /media/ {
        # if asset versioning is used
        if ($query_string) {
            expires max;
    location /admin/media/ {
        # this changes depending on your python version
        root /path/to/test/lib/python2.6/site-packages/django/contrib;
    location / {
        proxy_pass_header Server;
        proxy_set_header Host $http_host;
        proxy_redirect off;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme $scheme;
        proxy_connect_timeout 10;
        proxy_read_timeout 10;
        proxy_pass http://localhost:8000/;
        # what to serve if upstream is not available or crashes
        error_page 500 502 503 504 /media/50x.html;
share|improve this question
up vote 8 down vote accepted

server_name defaults to an empty string, which is fine; you can exclude it completely.

Another common approach for the "I don't want to put a name on this" need is to use server_name _;

Your URL won't work with this config, though; you're only listening on port 80. You'd need to add a listen 9050; as well.

share|improve this answer
thanks! I'll try it out! – bash- Jan 19 '12 at 17:07
hey can you take a look at this… – Muhammad Umer Mar 26 '15 at 18:20
somewhat related – Muhammad Umer Mar 26 '15 at 18:21

server_name _; is not a wildcard see here:

just specify the default_server directive for ip-only access (see

server {
    listen default_server;
share|improve this answer
It's discouraged to simply link to the useful piece of information and not include it in your answer - in this case that the server_name _; is a non-match. – BE77Y Feb 20 '15 at 9:01
"is not a wildcard" == "is a non-match". I'm sure they'll get it. – Joe Feb 21 '15 at 1:06
The two aren't equal; non-match is what is served when nothing else matches, whilst a wildcard matches everything. The point here however is that the useful information should be in the answer, not linked on some other site (however well presented on that site), as detailed here – BE77Y Feb 21 '15 at 8:50
And the point is that this is not a 'good answer' but it's an answer. Sorry no time. If you would like to edit/rewrite it, I give you full permission to. Otherwise, they will know exactly what to do, and it is helpful. Feel free to rewrite it, otherwise the answer stands. – Joe Feb 21 '15 at 19:32
If you had 'no time' to include an extra line with the pertinent information, I honestly don't know why you bothered to answer a 3 year old post with an accepted answer! – BE77Y Feb 21 '15 at 22:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.