Arch Linux

milogert

Member

Registered: 2016-02-10

Posts: 12

Best way to organize servers in nginx

Hopefully this has not been asked. I did a search and didn't see anything.

My router does not support NAT loopback (i.e. I cannot access my domain "example.com" within my own domain).

I currently organize my web services like:

• rss.example.com - my rss feed reader

• adminer.example.com - my adminer instance

• usenet.example.com/* - my usenet services

Given that I cannot use subdomains for local network names (like rss.localserver), what is the best way to organize my server blocks in nginx for each of these services? Below are some "external" server blocks (ones that would be hit from outside my network).

While I am asking for the best way, I am also asking if there is even a good way to do this or if the best option might be to just get a router with NAT loopback.

server {
    include conf/ssl-example.com.conf;
    server_name rss.example.com;
    root /usr/share/webapps/tt-rss;

    location / {
        index index.php;
    }
    include conf/php.conf;
}

server {
    include conf/ssl-example.com.conf;
    server_name usenet.example.com;

    location /service1 {
        proxy_pass http://localserver:8081;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forward-for $remote_addr;
    }

    location /service2 {
        proxy_pass http://localserver:8082;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forward-for $remote_addr;
    }
}

yodermk

Member

Registered: 2012-07-17

Posts: 86

Re: Best way to organize servers in nginx

If a small number of internal hosts, you could set everything up in /etc/hosts.
If a larger number, you could run internal DNS.
Then you don't need a router NAT loopback.  Or am I missing something?