I would not think this to be possible because you cannot establish a non-secure connection to a mumble server (if my understanding is correct). Load balancing http servers is easy due to the design, but with mumble the cert is a part of the start up and key to the connection itself.
Perhaps you could have the cert on the balancer and the server, but how would multiple connections talk to each other if the balancer puts them on 2 separate servers?
https://sourceforge.net/p/mumble/discussion/492607/thread/b4c38b63/
You'll also be charged if you go over limit on AWS. I don't know (and won't ask) for your locale, but as I said, look for cheap providers in your area, you can probs get $5/month without too much hassle. Just need to do local googling.
DigitalOcean has a very clear guide on installing Murmur within their system and here's the Mumble Wiki page for more info.
The firewall/ports config will depend on your exact distribution of OS, but the official OS docks + stackoverflow will fix it for you, I am pretty certain.
Let me know if Ethervane ActiveHotkeys works for you. Here's a screenshot of my key bind (,), after Mumble opens. When it closes, and I test the hotkeys again, it says No under Active.
As far as the mouse goes, if all else fails, maybe try HotKey Commander. To me, it sounds like something is grabbing focus and re-assigning the global hotkey and mousekeys on certain events. Perhaps check eventvwr.msc to see if there are any errors at or around the time you lose your keybind.
I do pretty much the same thing. Got my mumble server cert via the EFF and certbot, which is free. But you need to own a domain.
When it comes to logging on without a password using a cert, you can create that cert yourself, then trust it as the Admin user on your mumble server.
That make sense? I think you're looking for certbot but you said you "both" want certificates. You only need a class 1 cert for the server, not for the users. They can use self-signed certs that the server then trusts and associates with their accounts.
It depends on how you installed mumble, but two things to check :
sslCiphers
in the murmur configuration is commented outIf after that you still have the warning, it may indicate that your Ubuntu version is pretty old and you should upgrade.
I would have suggested to use a static build of murmur as a workaround, but apparently the OpenSSL (encryption) library it uses is outdated too.