FAQ for KH Connection
Here are some questions you might have regarding the Remote KH Connection
What do I need to connect?
You can connect from any device that uses a modern browser (such as FireFox, Safari or Chrome).
There have been some issues with connecting using Chrome but nothing a simple page refresh shouldn't resolve.
What if I can't connect?
If you are unable to connect to the server (https://kasm.thelanges.us) just try to refresh the page, the issue should be temporary and hopefully will be resolved shortly.
If it isn't resolved quickly just call Ben and tell him his server is bad and he should feel bad.
What if I still can't connect but need access?
If you still can't connect but need access remotely, you can always fall back to using TeamViewer. The installation is still active on the machine but is limited due to licensing issues and overutilization.
What if Ben gets hit by a bus?
The "Bus Convergence Factor" on this deployment is 1. Meaning it will only take 1 bus to eliminate necessary functional resources and cause a persistent system outage of the service.
If that happens please take care of my family.
Also just use TeamViewer, it is still on the machine and will keep working as it always has.
Alternatively the core components of the remote connection (TailScale) are signed in using the KH account and can be utilized directly circumventing the front end deployment.
This is cool, how does it work?
The system connects remotely to the machine with RDP via a private mesh network run on TailScale.
RDP : This is the standard Remote Desktop Connection Protocol that is built into Windows Operating Systems
TailScale : This is a mesh VPN networking product that creates a point to point WireGuard based VPN Mesh and is coordinated via the TailNet system. It is free for limited use and the key software components are open source and available for forking if need be.
Kasm : This is an open source Container Streaming platform that also functions as a HTTPS based Remote Desktop Gateway and desktop streaming application. It leverages a TailScale connection on the server to route the RDP session directly to the KH computer and then streams the session via HTTPS using Guacamole for web sessions or direct HTTPS via a session broker for RDP connections.
Here is a diagram of how it works:
RentonKHPC <-> TailScale <-> RDP <-> KASM Server <-> Client session
Is this free and are we abiding to all licensing agreements?
Yes, all the utilities, platforms and software are being used according to their proper license agreements. The core pieces are either free or hosted on private hardware that has been donated for this purpose.