JamiePhonic

This option is specifically for encrypting the connection between Guac and the database itself using SSL. It's mostly a non issue in docker environments since the traffic either never leaves the container becasue Guac and MariaDB (MySQL) are both in the same container, or it never leaves the host since Guac and Database containers are "attached" to the same network and linked to each other by docker. It's really only something you'd want to consider configuring if your Guac instance and Database were on completly different servers. Not uncommon in Corporate environments, none the less, it never hurts to implement best practice security

@Hugh Jazz I had this problem also. I solved it by adding the following to my guacamole.properties file. mysql-ssl-mode: disabled You can also set it to 'preferred' so it will use SSL automatically if you configure it in the future and fall back to insecure otherwise.

You are most likely still protected, however the "Back-UPS" units are usually more intended for small, lower power devices like your router or cordless phone. While they can be connected to computers, the information they output over USB to the host is usually only "core" information about line conditions, battery voltage and estimated runtime. I believe the error you're getting means that either the ACPUPS service, or the UPS itself attempted to perform a self test (I believe APC UPS's perform self tests every 2 weeks), but that your UPS doesnt support reporting on it. It may be possible to perform one manually, however I would recommend stopping any Containers or VM's if you have them running and then stop the array (just in case) first, then try holding down the power button on the UPS for around 3 seconds. The power button should begin to flash and then go back to solid once the test is done. You can also try just unplugging the UPS from the wall and see if it holds. If it does, i'd recommend leaving it unplugged and letting it drain to around 30%. This should help re-calibrate the UPS's estimated runtime. It's also a good way to test if notifications (assuming you've configured a notification agent under `Settings => Notifications`) are working properly

The DNS record you want to update must already exist in order for it to be updated. If you deleted the record, you'll need to re-create it first. Check the containers log for any errors.

If you have more than one domain in your account, you may need to add an additional variable to the containter template to specify the perticular domain you want to update like i had to

i'm only updating a couple of specific sub domain A records for one of my domains so i can generate lets encypt certs for on site services (namley unifi so that guests dont get certificate warnings on the guest portal) while the website and email etc are hosted publicly on dedicated servers. I'm probably a bit of an edge case, but It wouldn't hurt to add the A record variable to the template with a default value of `@` in case others are in a similar position where they only want to update one specific sub domain record, or they have multiple domains. I think this was part of the problem i was having. I have more than one domain registered, but even providing the full domain name still gave me errors. It was only after i checked the documentation on your Repo and noticed the `A_Record` variable that i was able to get it working. Thanks again!

Hi there! First off, Thanks for this container. i've been trying to figure out an easy way to do this for a while! Second, i've noticed a flaw in the template. It seems like the template has the description for the `GODADDY_A_NAMES` variable assigned to the `GODADDY_DOMAINS` (`Domain Name`) variable, so entering just a comma seperated list of A records to update causes the script to fail with the same error that @broadcastthebadger (among others) got. I fixed this by adding the `GODADDY_A_NAMES` variable to the template and then filling in the info in the right places!

@Living Legend i've been running behind HAProxy for the past couple of years but i had to modify its config to keep tunnle conections from timing out in a handful of apps (Guac and HomeAssistant mainley): WebSocket connections are technically tunnels from HAProxy's prespective. Not sure if there's a similar config you could try in Nginx? defaults timeout tunnel 60s timeout connect 5s timeout client 5s timeout server 5s If you can post/link your Nginx config, it might help identify possible issues?

Thanks so much for all your hard work on this! Tested connections from a couple different locations (Via VPN) and the remote IP seems to be showing correctly!

Thanks for all your hard work on this container! I use this almost daily for various things. I was wondering if you'd be able to modify the default tomcat config the container ships with to include the Remote IP Valve: <Valve className="org.apache.catalina.valves.RemoteIpValve" remoteIpHeader="x-forwarded-for" /> This would allow Guacamole's connection history page to reflect the correct source IP for people using a reverse proxy like NGINX or HAProxy. Currently, i'm doing it by adding "/bin/bash /config/startup.sh" to the containers "post arguments" which copies a modified "server.xml" that includes the valve over the existing one, then exec's "/etc/firststart/firststart.sh" to continue starting the container as usual. Don't get me wrong, It works, but it's basically a bodge