Skip to main content

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.

Remote Desktop in Termix brings graphical desktop access and legacy terminal protocols into the same interface you use for SSH. Powered by Apache Guacamole, it streams RDP, VNC, and Telnet sessions directly in your browser — no plugins, no separate client, no additional software on your workstation.

Supported connection types

RDP

Connect to Windows servers and desktops using the Remote Desktop Protocol. Full graphical desktop access rendered in the browser.

VNC

Access Linux desktops, KVM guests, or any system exposing a VNC server. Works with most VNC implementations.

Telnet

Connect to legacy network devices and systems that still rely on Telnet for configuration or management.

Key capabilities

Just like SSH terminals, remote desktop sessions can be arranged in split-screen mode. View multiple sessions side by side in the same browser window.
Configure connection settings per host — including resolution, color depth, and protocol-specific options — to match the requirements of each remote system.
Remote desktop connections are managed alongside your SSH hosts. Each host can have its connection type, credentials, and settings saved independently.

Requirements

Remote desktop features require the guacd service to be running and reachable by Termix. If you are using Docker Compose, include the guacd container in your deployment. Without it, RDP, VNC, and Telnet connections will not be available.
The Termix Docker Compose setup includes guacd on the same internal network:
docker-compose.yml
services:
  termix:
    image: ghcr.io/lukegus/termix:latest
    container_name: termix
    restart: unless-stopped
    ports:
      - "8080:8080"
    volumes:
      - termix-data:/app/data
    environment:
      PORT: "8080"
    depends_on:
      - guacd
    networks:
      - termix-net

  guacd:
    image: guacamole/guacd:1.6.0
    container_name: guacd
    restart: unless-stopped
    ports:
      - "4822:4822"
    networks:
      - termix-net

volumes:
  termix-data:
    driver: local

networks:
  termix-net:
    driver: bridge
If you only plan to use SSH features and do not need RDP, VNC, or Telnet, you can omit guacd and the shared network from your Docker Compose file to keep the deployment minimal.

Build docs developers (and LLMs) love