Differences

This shows you the differences between two versions of the page.

--- configure_apache_virtual_host_ubuntu_server_act_proxy_origin_iis_same_local_network [2023/07/17 05:04] – wikiadmin
+++ configure_apache_virtual_host_ubuntu_server_act_proxy_origin_iis_same_local_network [2023/07/17 05:05] (current) – wikiadmin
@@ Line 3: / Line 3: @@
 Let's say you have two servers within a local area network, each of which is behind (on the "backend" or LAN-side) of the same network router that has only one public static IP address configured on the WAN side (frontend) of that router. Furthermore, let's say the operating system on one of those servers is Ubuntu Server 22.04 LTS running Apache2 webserver and hosting various websites and apps, and that the operating system on the other server is Microsoft Windows Server 2012 or 2019 running IIS 10 web server installed, and hosting various websites.  Both web servers are listening on TCP ports 80 and 443; however, the network router can only be configured to port forward TCP ports 80 and 443 to one server on the LAN.  Each of these two servers is obviously bind to separate local network IP addresses (not routable on the internet), and the local network is, for our example, configured for 192.168.1.0/24.
-**Our Goal?  We want to be able to host and publicly serve websites from both of the two webservers from the single static public IP address configured on the WAN side of the router.**
+**Our Goal?  We want to be able to host and publicly serve websites from each of the two webservers from the single static public IP address configured on the WAN side of the router.**
 The problem is that the router can only port forward the standard Web TCP ports 80 (http) and 443 (https) to a single local IP address that is bind to one of the two webservers on the backend.