SBN - Proxy Server Notes - Revision history

Tinker: /* Reverse Proxy (Outside Access to internal servers) */

2020-07-16T01:59:22Z

Reverse Proxy (Outside Access to internal servers)

2020-07-15T17:22:13Z

Reverse Proxy (Outside Access to internal servers)

2020-07-15T17:21:47Z

Reverse Proxy (Outside Access to internal servers)

2020-07-02T06:00:35Z

Upcoming tricks...

2020-07-02T05:53:52Z

2020-06-28T21:37:17Z

2020-06-28T21:32:26Z

Reverse Proxy (Outside Access to internal servers)

2020-06-27T06:17:08Z

Reverse Proxy (Outside Access to internal servers)

2020-06-27T05:24:15Z

Reverse Proxy (Outside Access to internal servers)

2020-06-24T18:38:03Z

Access Control by IP / HostName

← Older revision		Revision as of 01:59, 16 July 2020
Line 17:		Line 17:

	You may have noted while setting up the '''VirtualHost''' that we're pointing at a set of [[NetMan - SSL Certs\|cert files]] that need to be on '''both''' machines. I would suggest that you obtain the certs on the main web server & copy them to the machine being proxied as this will (to some extent) simplify updating them.		You may have noted while setting up the '''VirtualHost''' that we're pointing at a set of [[NetMan - SSL Certs\|cert files]] that need to be on '''both''' machines. I would suggest that you obtain the certs on the main web server & copy them to the machine being proxied as this will (to some extent) simplify updating them.
		+
		+	* [[NetMan - SSL Certs#Installing on a Webserver that will be proxied\|Installing on a Webserver that will be proxied]]

	Also, 2 log files in a new folder...		Also, 2 log files in a new folder...

@@ Line 14: / Line 14: @@
 *[[WebServer - Proxy VirtualHost Configuration|Proxy VirtualHost Configuration]]
-*See [[WebServer - Name-based Virtual Host Support|Name-based Virtual Host Support]]
+*See also:  [[WebServer - Name-based Virtual Host Support|Name-based Virtual Host Support]]
 You may have noted while setting up the '''VirtualHost''' that we're pointing at a set of [[NetMan - SSL Certs|cert files]] that need to be on '''both''' machines.  I would suggest that you obtain the certs on the main web server & copy them to the machine being proxied as this will (to some extent) simplify updating them.

← Older revision		Revision as of 17:21, 15 July 2020
Line 13:		Line 13:
	Create the virtual host to point incoming connections at the internal server you want to proxy:		Create the virtual host to point incoming connections at the internal server you want to proxy:

		+	*[[WebServer - Proxy VirtualHost Configuration\|Proxy VirtualHost Configuration]]
	*See [[WebServer - Name-based Virtual Host Support\|Name-based Virtual Host Support]]		*See [[WebServer - Name-based Virtual Host Support\|Name-based Virtual Host Support]]

← Older revision		Revision as of 06:00, 2 July 2020
Line 51:		Line 51:
	==Upcoming tricks...==		==Upcoming tricks...==

		+	*Access control by User Login
		+	**[https://httpd.apache.org/docs/2.4/howto/auth.html Apache Authentication and Authorization]
	*Multi-Site Server Management from a Central Server		*Multi-Site Server Management from a Central Server

← Older revision		Revision as of 05:53, 2 July 2020
Line 57:		Line 57:
	*[https://httpd.apache.org/docs/2.4/mod/mod_proxy.html Apache Module mod_proxy]		*[https://httpd.apache.org/docs/2.4/mod/mod_proxy.html Apache Module mod_proxy]
	*[https://httpd.apache.org/docs/2.4/mod/mod_authz_host.html Apache Module mod_authz_host]		*[https://httpd.apache.org/docs/2.4/mod/mod_authz_host.html Apache Module mod_authz_host]
		+	*[https://httpd.apache.org/docs/2.4/howto/reverse_proxy.html Apache Reverse Proxy Guide]

@@ Line 11: / Line 11: @@
 (possibly add <code>mod_authz_host</code> to the list...)
-Create the virtual machine to point incoming connections at the internal server you want to proxy:
+Create the virtual host to point incoming connections at the internal server you want to proxy:
 *See [[WebServer - Name-based Virtual Host Support|Name-based Virtual Host Support]]
-You may have noted while setting up the '''VirtualHost''' that we're pointing at a set of cert files that need to be on '''both''' machines.
+You may have noted while setting up the '''VirtualHost''' that we're pointing at a set of [[NetMan - SSL Certs|cert files]] that need to be on '''both''' machines.  I would suggest that you obtain the certs on the main web server & copy them to the machine being proxied as this will (to some extent) simplify updating them.
 Also, 2 log files in a new folder...

@@ Line 13: / Line 13: @@
 Create the virtual machine to point incoming connections at the internal server you want to proxy:
-*<code>sudo vim /etc/apache2/apache2.conf</code>
+*See [[WebServer - Name-based Virtual Host Support|Name-based Virtual Host Support]]
-& add this (modified to suit) to the end of the file:
+You may have noted while setting up the '''VirtualHost''' that we're pointing at a set of cert files that need to be on '''both''' machines.
 Also, 2 log files in a new folder...
@@ Line 56: / Line 21: @@
 *<code>sudo mkdir /var/log/apache2/Proxy</code>
-(this folder will be populated automgically when you restart Apache...)
+(this folder will be populated automagically when you restart Apache...)
 Now, restart Apache:
@@ Line 62: / Line 27: @@
 *<code>sudo service apache2 restart</code>
-At this point, you should be able to browse to '''MyServer.MyDomain.net''' from outside your network.
+At this point, you should be able to browse to '''Proxy.foo.bar''' from outside your network.
 ==Special considerations for the ESXi WebUI==

@@ Line 48: / Line 48: @@
 You may have noted that we're pointing at a set of cert files that need to be on the machine.
-*<code>sudo mkdir /etc/letsencrypt/live/MyServer.MyDomain.net</code>
+*<code><s>sudo mkdir /etc/letsencrypt/live/MyServer.MyDomain.net</s></code>
 <s>& copy the certs from the internal server into this folder. (see [[CertGetter]] for information about getting certs for internal machines)</s>

@@ Line 82: / Line 82: @@
 [http://httpd.apache.org/docs/2.2/howto/access.html#host Reference]
-In theory, You could also replace the IP addresses with hostnames (or partial hostnames). '''BUT''', those hostnames need to be visible accross the internet...
+In theory, You could also replace the IP addresses with hostnames (or partial hostnames). '''BUT''', those hostnames need to be visible across the internet...
 ==Upcoming tricks...==