Hi, and many thanks for your reply. I think I found the culprit. I run both Nginx and Guacamole in docker containers, and as they use different networks, Nginx is not able to "see" into the Guacamole container even though I use the host IP. In my case, Nginx is in a NAT'ed with 10.13.0.3 as IP while Guacamole is in a Bridged net with 174.32.1.7 as IP. The host is 192.168.1.10.
If I SSH into the Nginx container and issue curl http://192.168.1.10:8080 it just times out after a while. As when I issue the same command from the host, it works. Do you have any idea how to add routing config to Nginx so that this can work? Rgds Oyvind November 29, 2022 4:57 PM, "Sean Hulbert" <[email protected]> wrote: > What I read here seems to be more DNS related. > > You can use your external or internal DNS and make an A record MY for your > DOMAIN.COM if your > client systems use the DNS internally it will resolve to the IP address of > the A records in the > DOMAIN.COM zone. Public DNS servers are same steps, only difference you are > using a public IP > address with the A record for all to resolve. > > If you do not have a DNS server you can use hosts records. > > If you are using the Docker image here is a good example > https://hub.docker.com/r/jlesage/nginx-proxy-manager > > If you are using NGINX look at doing a location using the loopback + port > > Thank You > Sean Hulbert > > Founder / CEO > Work Ph: 925.663.5565 > > Security Centric Inc. > A Cybersecurity Virtualization Enablement Company > We don't just run you through the motions, Our labs teach you how to think! > > System Award Management > CAGE: 8AUV4 > > AFCEA San Francisco Chapter V.P. > > If you have heard of a hacker by name, he/she has failed, fear the hacker you > haven’t heard of! > > CONFIDENTIALITY NOTICE: This communication with its contents may contain > confidential and/or > legally privileged information. It is solely for the use of the intended > recipient(s). Unauthorized > interception, review, use or disclosure is prohibited and may violate > applicable laws including the > Electronic Communications Privacy Act. If you are not the intended recipient, > please contact the > sender and destroy all copies of the communication. Content within this email > communication is not > legally binding as a contract and no promises are guaranteed unless in a > formal contract outside > this email communication. > > igitur qui desiderat pacem, praeparet bellum!!! > > Epitoma Rei Militaris > > -----Original Message----- > From: Nick Couchman [[email protected]] > Sent: Tuesday, November 29, 2022 7:31 AM > To: [email protected] > Subject: Re: Hos to use Nginx Proxy Manager as Reverse Proxy to access > Guacamole remotely > > On Tue, Nov 29, 2022 at 4:46 AM <[email protected]> wrote: > >> Hi all, >> >> My objective is to use JLesage Nginx Proxy Manager v2.9.19 (NPM) to access >> Guacamole v1.3.0 >> remotely. >> This requires resolving the following: my.domain.com ---> >> https://192.168.x.x:8080/guacamole >> >> I have not been able to figure out how to configure NPM to achieve this. >> >> Do anyone have a successful recipe for this? > > I am not sure how Nginx Proxy Manager differs from plain Nginx, but we have > instructions in the > Guacamole User Guide that detail how to set up proxying: > > https://guacamole.apache.org/doc/gug/reverse-proxy.html > > It covers both Apache HTTPD and Nginx. > > -Nick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
