Nexterm is distributed as Docker images and requires no additional runtime dependencies beyond Docker itself. This guide walks you through generating your encryption key, choosing a deployment topology, and accessing the web interface for the first time.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/gnmyt/Nexterm/llms.txt
Use this file to discover all available pages before exploring further.
Docker images
Nexterm provides three images depending on how you want to deploy:| Image | Description |
|---|---|
nexterm/aio | All-in-one — server, web client, and engine bundled in a single container. Recommended for most deployments. |
nexterm/server | Server only — Node.js backend and web client. Requires a separately deployed engine. |
nexterm/engine | Engine only — connection service handling SSH, VNC, RDP, and Telnet. Pairs with nexterm/server. |
nexterm/aio. For multi-network or distributed setups — for example, reaching servers on isolated subnets — deploy nexterm/server with one or more nexterm/engine instances on the relevant networks.
Before you begin
Nexterm encrypts stored credentials using a key you supply at startup. Generate a strong key before deploying:ENCRYPTION_KEY environment variable in every deployment command below.
All-in-one setup
Choose your network mode
Host network is strongly recommended because it gives Nexterm direct access to your host’s network stack — required for features like Wake-on-LAN and connecting to servers via
localhost. Use bridge network only when you need container-level network isolation.Host network mode makes Nexterm behave as if it is running directly on the host, so it can reach any service accessible from the host — including
localhost addresses and services on other local interfaces.Docker Compose
If you prefer Docker Compose, use one of the following files. Save it asdocker-compose.yml, then run docker compose up -d.
Split deployment (server + engine)
Use this topology when you need the engine to run on a different network segment, or when you want to connect multiple engines to a single server.Create the engine configuration file
Create a
config.yaml file for the engine. Set server_host to the hostname or IP of your server container, and leave registration_token empty — the server generates a token automatically on startup.IPv6 support
When using bridge networking, Nexterm cannot reach IPv6 addresses by default. To enable IPv6 connectivity, add a custom network withenable_ipv6: true to your existing docker-compose.yml:
IPv6 configuration is only needed with bridge networking. Host network mode already inherits full IPv6 support from the host.
First login
After starting Nexterm, openhttp://your-server:6989 in your browser. On first launch, Nexterm prompts you to create an admin account. Enter your desired username and password to complete setup.