Serve static content through subdomain in nginx

Question

I have some slate docs as website and would like to serve them on the internal server, through a subdomain as follows: internal-docs.mysite.com. For the record, accessing mysite.com shows the "nginx is running propertly" page.

I've created a config file with following path and name: /etc/nginx/sites-available/internal-docs.mysite.com:

server {
    listen 80;
    server_name internal-docs.mysite.com;

    root /var/www/docs-internal;
    index index.html;

    location / {
        # First attempt to serve request as file, then
        # as directory, then fall back to displaying a 404.
        try_files $uri $uri/ =404;
    }

    error_page 404 /404.html;
}

And of course, I've put the files in /var/www/docs-internal. And then I made a symlink to the uppershown config file in the /etc/nginx/sites-enabled dir:

internal-docs.mysite.com -> ../sites-available/internal-docs.mysite.com

Then I reload nginx -s reload but "this site can't be reached" error is what I get when accessing the URL.

The setup and configuration look correct to me (according to the guidelines I've followed), so that's why I'm in a dead end, sort of...

This does not seem to be a Nginx problem. Is your subdomain correctly pointing to the server (try a nslookup or ping of your subdomain) ? — Gabriel Hautclocq, Mar 07 '17 at 14:48
@GabrielHautclocq, are you saying that the configuration I set up sounds correct? Just so I know to look into something else regarding the problem. — Milkncookiez, Mar 07 '17 at 14:59
Also you should check that Nginx has read access to your config file, and that your conf loads .conf files inside the sites-enabled directory. — Gabriel Hautclocq, Mar 07 '17 at 15:03
We have one more site being served the exactly same way, so I just followed that setup that we already have. Should I make it listen on port `80`? I was not sure. Also, I checked and I think I will have to add the subdomain to the firewall config. — Milkncookiez, Mar 07 '17 at 15:08
Let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/137456/discussion-between-gabriel-hautclocq-and-milkncookiez). — Gabriel Hautclocq, Mar 07 '17 at 15:16

Gabriel Hautclocq · Accepted Answer · 2017-07-17T06:54:39.327

It seems you forgot the Listen directive. Try the following:

server {
    listen 80;
    server_name internal-docs.mysite.com;

    root /var/www/docs-internal;
    index index.html;

    location / {
        # First attempt to serve request as file, then
        # as directory, then fall back to displaying a 404.
        try_files $uri $uri/ =404;
    }

    error_page 404 /404.html;
}

If that does not work, check:

That Nginx user has read permission to the site content. For example if your Nginx user is www and you have root access, do the following:
```
# su www
$ cat /var/www/docs-internal/index.html
```
If that fails, ensure the location has correct ownership and permissions. Note that for a user to be able to browser a directory, that directory must have the execute bit for that user or user group.
That Nginx user has read permission on file ../sites-available/internal-docs.mysite.com. For example if your Nginx user is www and you have root access, do the following:
```
# su www
$ cat /etc/nginx/sites-available/internal-docs.mysite.com
```
If that fails, ensure that the config files have correct ownership. Note: normally Nginx master process is run by root, and that process spawns sub-processes run as Nginx user, so permissions on config files are unlikely to be the problem.
That maybe your config file name should end with ".conf" (on my server I have the following line: include conf.d/*.conf; so it will NOT load any conf file ending with ".com".
That Nginx tries to load files in ../sites-available/ in its main config file. Maybe it does not and looks instead in the conf.d directory (the default).
That you can do a ping and nslookup on the subdomain. If you cannot, then you have to fix that first (DNS, firewall...).

score 2 · Answer 2 · answered Mar 14 '17 at 13:25

For the sake of others - the configuration I wrote was correct, and my problem was in 2 things:

I had to remove the listen 80 directive, since there is another configuration file already, that specifies that nginx should listen on port 80. One should not tell nginx twice to listen on the same port, even if it's in two separate configuration files
Permissions on the /var/www/docs-internal folder. Opening a folder requires x (execute) permissions, while opening a file requires r (read) perm. I had to provide the according permissions to all the folders in this hierarchy, so that the content could be open globally (from everyone), which is basically accessing it from the browser.

Serve static content through subdomain in nginx

2 Answers2

Linked