Difference between revisions of "Reverse Proxy"

From East Essex Hackspace
Jump to navigation Jump to search
Line 10: Line 10:
 
== Traffic Path ==
 
== Traffic Path ==
  
user -> <something>.eehack.space -> cloudflare proxy with forced TLS termination -> EEH_IP:80 -> Mikrotik Router Nat 80:2095 whitelisting only cloudflare IPs -> docker_ip:2095 -> nginx container 2095:80 then routed via path or host based routing to final destination
+
user -> https://<something>.eehack.space -> cloudflare proxy with forced TLS termination -> EEH_IP:80 (http) -> Mikrotik Router Nat 80:2095 whitelisting only cloudflare IPs -> docker_ip:2095 -> nginx container 2095:80 then routed via path or host based routing to final destination

Revision as of 09:39, 8 July 2021

Reverse Proxy

Is a reverse proxy using nginx to present services hosted on the internal servers to the internet.

Host, port and path based routing is possible.

Configuration

https://github.com/eehackspace/eeh-reverse-proxy

Traffic Path

user -> https://<something>.eehack.space -> cloudflare proxy with forced TLS termination -> EEH_IP:80 (http) -> Mikrotik Router Nat 80:2095 whitelisting only cloudflare IPs -> docker_ip:2095 -> nginx container 2095:80 then routed via path or host based routing to final destination