NGINX as a reverse proxy for multiple domains

[JerryMungo]

.

 

[SauRoNZA]

I don't have the "right" answers for you having hacked mine together, but there are loads of examples here that should help somewhat.

GitHub - linuxserver/reverse-proxy-confs: These confs are pulled into our SWAG image: https://github.com/linuxserver/docker-swag

These confs are pulled into our SWAG image: https://github.com/linuxserver/docker-swag - linuxserver/reverse-proxy-confs

github.com

 

[Concentric]

you can also look at Traefik (i personally use it) and caddy

 

[The_Ogre]

@WAslayer

 

[WAslayer]

The NGINX docs makes them simple to understand, though bloated for most use cases.. I modified the simple example they provide, which should work fine for your use case here:

F5 NGINX Product Documentation

Learn how to deliver, manage, and protect your applications using F5 NGINX products.

www.nginx.com

server { # simple reverse-proxy

    listen       80;

    server_name  domain2.com www.domain2.com;

    access_log   logs/domain2.access.log  main;

 

    # pass requests for dynamic content to rails/turbogears/zope, et al

    location / {

      proxy_pass      http://127.0.0.1:8080;

    }

  }

 

[chewiesw]

I may just end up with an

http://myservers.com/app1
http://myservers.com/app2
http://myservers.com/app3

scenario - probably easier to manage as well.

I followed and altered this config to suit my needs

Configure NGINX as a Secure Reverse Proxy — REDELIJKHEID

NGINX (pronounced as engine-x) is a versatile (reverse) proxy service for Linux which can be used for many purposes. This post gives a relative small and easy example that I use at home for accessing insecure web services in my home. These are: Domoticz Free and opensource Domotica software S

www.redelijkheid.com

 

[WAslayer]

So would I duplicate that server section for each TLD (server1.myserver.com, server2.myserver.com, server3.myserver.com) since the proxy_pass will be to a different IP?

Yup, you will have 3 entries, one for each server..