Termix supports several installation methods. Docker Compose is the recommended approach for running the Termix server, as it handles all dependencies in a single file and makes upgrades straightforward. Native desktop and mobile clients are also available for every major platform and can connect to any self-hosted Termix server.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Termix-SSH/Termix/llms.txt
Use this file to discover all available pages before exploring further.
Docker Compose (recommended)
The Docker image is published atghcr.io/lukegus/termix:latest. The compose file below includes guacd, which is required for RDP and VNC remote desktop support. You can omit guacd and the termix-net network if you don’t plan to use remote desktop features.
Create a docker-compose.yml file
Copy the following into a new
docker-compose.yml file in a directory of your choice:docker-compose.yml
The
guacd container (Apache Guacamole Daemon) is required for RDP and VNC remote desktop sessions. If you only need SSH terminal access, you can remove the guacd service, its ports entry, the depends_on block from termix, and the networks sections entirely.Start the containers
Run the following command in the same directory as your Docker will pull the
docker-compose.yml:termix and guacd images on first run. This may take a minute depending on your connection speed.Environment variables
| Variable | Default | Description |
|---|---|---|
PORT | 8080 | Port the Termix web UI listens on. |
ENABLE_SSL | false | Set to true to enable HTTPS with automatic certificate generation. |
SSL_PORT | 8443 | Port for the HTTPS listener when SSL is enabled. |
SSL_DOMAIN | localhost | Domain name used when generating the SSL certificate. |
SSL_CERT_PATH | /app/data/ssl/termix.crt | Path to a custom SSL certificate file. |
SSL_KEY_PATH | /app/data/ssl/termix.key | Path to a custom SSL private key file. |
PUID | 1000 | User ID the Termix process runs as inside the container. |
PGID | 1000 | Group ID the Termix process runs as inside the container. |
Updating Termix
To update to the latest image, pull the new version and recreate the container:Native client installation
The Termix desktop and mobile clients can connect to any self-hosted Termix server, or run standalone without a backend for SSH-only use.- Docker
- Windows
- macOS
- Linux
See the Docker Compose instructions above. This is the recommended method for running the Termix server.Supported: Any Linux, Windows, or macOS host with Docker Engine or Docker Desktop installed.
Mobile
| Platform | Method |
|---|---|
| iOS/iPadOS (v15.1+) | Apple App Store or IPA sideload |
| Android (v7.0+) | Google Play Store or APK sideload |