<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">I already have nginx performing a
redirect to the same machine's Guacamole front end, which as you
know is a Tomcat app. So the way I have nginx configured now, when
it is hit with
https://<nginx-guac_machine_ip_address>:80/wxyz nginx is
converting that to <a class="moz-txt-link-freetext" href="http://127.0.0.1:8080/guacamole-1.1.0">http://127.0.0.1:8080/guacamole-1.1.0</a>. So I've
got two mechanisms in series here, in order pfSense and nginx,
that do mangling even without making use of internet DNS and I'm
trying to get the pfSense-nginx transition sorted such that
pfSense will make the intermediate connection between itself and
nginx and do so without breaking the https escalation.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 6/28/20 7:20 AM, Jim Kinney wrote:<br>
</div>
<blockquote type="cite"
cite="mid:E0DEE0C7-E264-44FE-972F-5613EA20FB87@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
I don't think pfsense will handle the /xyz->/abc layer. That's
just for the ngnx proxy.<br>
<br>
<br>
<div class="gmail_quote">On June 28, 2020 1:00:54 AM EDT, Jeff
Hubbs via Ale <a class="moz-txt-link-rfc2396E" href="mailto:ale@ale.org"><ale@ale.org></a> wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<pre class="k9mail">Now that I've got a static IP (just one) I'm starting to work on hosting
my own web servers and the first thing I'm trying to do is make a nginx
and Apache Guacamole rig export Windows Server Remote Desktop sessions
via HTML5 (that's the Guacamole part) out to people who come in with a
URL I give them. I do not yet have internet DNS involved so the URL I
plan to give to one person I want to demonstrate the capability to will
have the form https://<internet_ip_address>/abcd.
I have all this set up behind a pfSense machine. From behind the pfSense
machine, I can point a browser to a URL in the form of
http://<nginx-guac_machine_ip_address>/wxyz, log in to Guacamole, and I
get an RDP session on the adjacent Windows server painted in the browser
window. In fact, I've got nginx where if I start the URL with http: it
will "auto-escalate" to https: using a self-signed certificate. What I'm
unclear about is what needs to happen in pfSense such that 1) someone
over the internet can come in at .../abcd as described above and pfSense
will change that to .../wxyz and 2) the https escalation still gets handled.
I expect that I will be using the nginx-Guacamole server for other
internet-reachable services so I won't want to do anything that will
pave over that flexibility.
- Jeff<hr>Ale mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ale@ale.org">Ale@ale.org</a>
<a href="https://mail.ale.org/mailman/listinfo/ale" moz-do-not-send="true">https://mail.ale.org/mailman/listinfo/ale</a>
See JOBS, ANNOUNCE and SCHOOLS lists at
<a href="http://mail.ale.org/mailman/listinfo" moz-do-not-send="true">http://mail.ale.org/mailman/listinfo</a>
</pre>
</blockquote>
</div>
<br>
-- <br>
"no government by experts in which the masses do not have the
chance to inform the experts as to their needs can be anything but
an oligarchy managed in the interests of the few.” - John Dewey
</blockquote>
<p><br>
</p>
</body>
</html>