http://remote.aslanfrench.work:8080/guacamole/#/ Is bot going through your proxy, but rather directly to your guacamole’s tomcat.
If you search this mail list history you’ll find a couple of nginx config examples some of us shared. From: Aslan French <[email protected]> <[email protected]> Reply: [email protected] <[email protected]> <[email protected]> Date: 30 December 2020 at 19:36:02 To: [email protected] <[email protected]> <[email protected]> Subject: Need some help troubleshooting a guac installation Hi, > > My name is Aslan. I'm a design technologist. I'm not a particularly good > developer or sysadmin but I dabble in running cloud apps for my own > personal needs on a homelab server. I wanted to set up Apache Guacamole so > that I could manage my homelab server remotely while I'm away from home. I > can ssh in of course, but sometimes it would be nice to have access to a > GUI. > > My homelab server already has Nextcloud and an nginx proxy server > installed on it. > > I tried following a combination of these tutorials to install Guac on my > homelab server: > > > https://www.linuxbabe.com/ubuntu/apache-guacamole-remote-desktop-ubuntu-20-04 > > https://www.howtoforge.com/how-to-install-and-configure-guacamole-on-ubuntu-1804/ > > When I visit http://remote.aslanfrench.work:8080/guacamole/#/ from the > homelab server I can see the Guac login. When I try to login it stalls out > on me. > > When I try to access that url from my laptop it hangs and does not work. > > Here is my nginx conf: > > ``` >> server { >> listen 80; >> listen [::]:80; >> >> # ## ssl cert location >> # location /.well-known/acme-challenge { >> # root /var/www/letsencrypt; >> # default_type "text/plain"; >> # try_files $uri =404; >> # } >> >> server_name remote.aslanfrench.work; >> access_log /var/log/nginx/guac_access.log; >> >> error_log /var/log/nginx/guac_error.log; >> >> # reroute all other traffice to the 443 port >> location / { >> return 301 <a href="https://$server_name:443;";>https:// >> $server_name:443; >> } >> >> } >> >> >> # # HTTPS stuff >> server { >> listen 443 ssl http2 default_server; >> listen [::]:443 ssl http2 default_server; >> server_name remote.aslanfrench.work; >> >> access_log /var/log/nginx/guacamole.access.log main; >> error_log /var/log/nginx/guacamole.error.log warn; >> >> # root /var/www/guacamole; >> # index index.html; >> >> location /guacamole/ { >> proxy_pass http://remote.aslanfrench.work:8080/guacamole/; >> proxy_buffering off; >> proxy_http_version 1.1; >> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; >> proxy_set_header Upgrade $http_upgrade; >> proxy_set_header Connection $http_connection; >> # access_log off; >> } >> } >> >> ``` >> > > That conf is based off of the nextcloud conf I'm using and the official > Guac manual. > > I successfully can access the root page commented out from any external > computer so I know that the proxy is at least working on some level > correctly. > > Generally speaking though that's something I'm kind of confused about? I > don't know anything about tomcat. The way the nginx proxy works is pretty > self explanatory I feel with most stuff. Nextcloud is PHP. so you just > point the nextcloud conf towards /var/www/Nextcloud and the index.php does > the rest. But what is the guacamole conf in the nginx supposed to be > pointing towards? "Where" in my filesystem is Guac located? I know "where" > nextcloud is located but I don't get how that works with Guac. Is that the > .war file? That's the guac webapp I guess? How does the nginx know where > that is located if I don't specify that anywhere in the conf file? It > apparently does since I can access guac's front locally (though maybe > that's not quite right since it's not accessible externally) > > Anyway, lots of questions here, and I def would appreciate any > troubleshooting tips anyone could provide. > *____**_**_* > > > *Aslan French* > *jackalope.tech* <http://jackalope.tech> | Design Technologist > > >
