From e47b3e402107fde8c4b51bc5bcece2644a57227d Mon Sep 17 00:00:00 2001 From: Athanasius Date: Wed, 19 May 2021 11:32:42 +0100 Subject: [PATCH] docs/Running: Correct and clarify the Apache Proxy examples. --- docs/Running-this-software.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/Running-this-software.md b/docs/Running-this-software.md index 2b4966b..2bac49d 100644 --- a/docs/Running-this-software.md +++ b/docs/Running-this-software.md @@ -74,7 +74,7 @@ If you're already using another web server, such as Apache, you'll need to duplicate at least the use of a TLS certificate and the Reverse Proxying as required. -For Apache you reverse proxy using something like the following in an +For Apache you would reverse proxy using something like the following in an appropriate `` section: @@ -83,9 +83,9 @@ appropriate `` section: ProxyPreserveHost On # Pass through 'gateway' upload URL to Debian VM - ProxyPass "/eddn/upload/" "https://EDDNHOST:8081/upload/" + ProxyPass "/upload/" "https://EDDNHOST:8081/upload/" # Pass through 'monitor' URLs to Debian VM - ProxyPass "/eddn/" "https://EDDNHOST/" + ProxyPass "/" "https://EDDNHOST/" ## In the 'eddn' account @@ -282,6 +282,10 @@ If using Apache on a Debian server then you need some ProxyPass directives: ProxyPass "/eddn/" "https://VM_HOST/" +This assumes you don't have a dedicated virtual host in this case, hence the +"/eddn" prefix there. Remove that if you are using a dedicated virtual host +on the 'existing server'. + You'll also need to redirect the Gateway and Relay ports using firewall rules. With iptables: