Skip to main content
Microsoft
separator
https://catalogartifact.azureedge.net/publicartifacts/cloudimg1647283583153.termix-ubuntu-24-04-54d9e040-37c5-41c3-8338-1b9baa74d367/image2_logolarge.png

Termix on Ubuntu 24.04 LTS

by cloudimg

Termix, self hosted browser based SSH terminal and server manager, on Ubuntu 24.04 LTS by cloud

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

Termix - Browser Based SSH Terminal and Server Manager by cloudimg

Deploy a private, self-hosted server management platform on your own Azure infrastructure in minutes. Termix 2.5.1 gives you a full SSH terminal with tabs and split panes, an SFTP file manager, port forwarding tunnels, and RDP, VNC and Telnet remote desktop sessions, all in a browser and all against servers you own. Connections live in one central inventory with folders and tags, and credentials including SSH private keys are held in an encrypted database rather than plain config files.

Why This Image Instead of Manual Installation

Termix ships as a container image and is built from TypeScript sources. Installing it on a server by hand means provisioning a Node.js 22 toolchain, compiling the frontend and backend, rebuilding native modules, writing a systemd unit, deriving an nginx reverse proxy covering twelve backend services and their websockets, and separately deploying the guacamole proxy for remote desktop. This image removes that work:

  • Termix 2.5.1 built from the pinned upstream release and managed by systemd
  • nginx serving the interface on port 80 and proxying every backend service and websocket
  • guacd installed and running, so RDP and VNC work without extra setup
  • No account ships: you create your own administrator on first visit
  • Four independent 256 bit secrets generated on your own VM at first boot
  • Every backend service bound to loopback; only SSH and the web interface are reachable
  • 24/7 cloudimg support for deployment, upgrades, TLS and access configuration

Use Case: One Console For Your Whole Fleet

An engineering team is tired of scattered SSH configs, keys copied between laptops, and no record of who connected to what. With this image they launch a VM, create their own administrator on first visit, add their servers once with folders and tags, and store the keys centrally in an encrypted vault. Everyone then works from the same inventory in a browser - terminal, file transfer, tunnels and remote desktop - inside their own VNet, on infrastructure they control.

Application Stack

Termix is a Node.js backend with a React frontend. The backend runs twelve services covering the REST API, the terminal websocket, tunnels, the SFTP file manager, host metrics, the dashboard, container management, the guacamole and container console websockets, tmux monitoring, serial console and the homepage. nginx serves the compiled frontend on port 80 and reverse proxies each of those, including websocket upgrades. guacd provides the RDP, VNC and Telnet transport. State lives in an encrypted SQLite database under /var/lib/termix, owned by a dedicated service account with mode 0700.

Secure By Default

The image ships with no user account, so there is no shared or default credential to change and nothing sensitive ships in the image. Because that first-run form is open until you complete it, and because this product holds SSH credentials for your other machines, restrict port 80 to your own address before first boot, create your administrator immediately, then turn off self-registration.

The secrets that sign sessions and encrypt the credential store are generated from the system random source on your own VM at first boot, so no two deployments share key material. Each user's data encryption key is unwrapped only by their own password at sign in. All twelve backend services and the guacamole proxy bind to loopback, leaving only SSH and the web interface network reachable. Every websocket, including the interactive terminal, verifies the session inside its connection handler and refuses unauthenticated connections. Termix also verifies each managed server's SSH host key on first connection.

Getting Started

1. Launch the image with port 80 restricted to your own address 2. Browse to the VM public IP and complete the create account form 3. Turn off self-registration from the Admin panel 4. Add your first server under Hosts, accept its host key fingerprint, and open a terminal 5. Terminate TLS before production - the image serves plain HTTP

Licensing and Pricing

Termix is licensed under Apache-2.0 and is free; there is no per-seat fee. The cloudimg charge of 0.04 US dollars per vCPU hour covers packaging, security patching, image maintenance, and 24/7 expert support. Restrict the web interface to trusted networks and terminate TLS before production.

Termix is a trademark of its respective owner. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

At a glance

https://catalogartifact.azureedge.net/publicartifacts/cloudimg1647283583153.termix-ubuntu-24-04-54d9e040-37c5-41c3-8338-1b9baa74d367/image0_screenshot01.png
https://catalogartifact.azureedge.net/publicartifacts/cloudimg1647283583153.termix-ubuntu-24-04-54d9e040-37c5-41c3-8338-1b9baa74d367/image5_screenshot02.png
https://catalogartifact.azureedge.net/publicartifacts/cloudimg1647283583153.termix-ubuntu-24-04-54d9e040-37c5-41c3-8338-1b9baa74d367/image4_screenshot03.png
https://catalogartifact.azureedge.net/publicartifacts/cloudimg1647283583153.termix-ubuntu-24-04-54d9e040-37c5-41c3-8338-1b9baa74d367/image6_screenshot04.png
English (United States)
Your Privacy Choices Opt-Out Icon Your Privacy Choices
Consumer Health Privacy Sitemap Contact Us Privacy & Cookies Terms of Use Trademarks About our ads Manage cookies