Guacamole VS Nginx Proxy Manager

Remote access for 10 people / end user access = Apache guacamole https://guacamole.apache.org/ - centralises access and audit and levels of access - MFA - HTML5 so all the enduser needs is a modern OS. Source: 5 months ago

I use wakeonlan for all of my machines, and configure Guacamole to push the WOL packet, delay 30-300 seconds (depending on machine) and then give me a terminal session to the server. Source: 5 months ago

Setup Guacamole. It handles SSH, VNC, and RDP via HTML5. Works fine with LDAP or even Active Directory authentication. Apache Guacamole - https://guacamole.apache.org/ I think you can preload a database with connections also so you could likely automate most of this away. Source: 5 months ago

Guacamole - To access Windows hosts via RDP. Source: 5 months ago

Use a vnc/rdp tool with a web interface (like https://guacamole.apache.org/) to access your remote host. Source: 6 months ago

Take a look at NginxProxyManager. This would give you the opportunity to put everything in the form of service1.domain.com , service2.domain.com ,etc. Source: 5 months ago

So I'm going into the log folder and I'm getting this error. It started maybe a week ago. Some of my host will go through, but if the do, its super slow. Others just out right refuse. I've tried deleting nginx entirely and still comes to the same error. I had nginx running for a few months now, but this got started. To be clear, this is what I've been using https://nginxproxymanager.com/ . I don't know if there is... Source: 9 months ago

Hi! I am setting up a home server where I host a number of different services that I want to be accessible exclusively through a proxy (Nginx Proxy Manager). What I mean is that if I serve a website on port 8081, for example, and I try to browse to the server's IP and that port, I won't be able to find the website. Instead I will have to browse to the IP and port that the proxy I set up has configured for that... Source: 9 months ago

As far as website hosting, just set up a few Docker containers: one for a web-server of your choice, and one for a reverse proxy. I recommend Nginx Proxy Manager. It handles SSL certificates for you in a super simple way (both the initial acquisition process as well as auto renewal) and makes it easy to expand to using multiple web servers in the future, or setting up redirects without filling up your DNS records. Source: 10 months ago

I'm trying to set up Nginx Proxy Manager on an existing box. Since it's already set up with a few services I don't want to mess with, and a firewall I don't particularly want to migrate (nftables, a good solution that docker apparently doesn't play nice with), I turned off docker's iptables management (despite the warnings, yes). Source: 10 months ago