Web Endpoint
Open a host's web UI inside Termix, directly or over an SSH tunnel.
- Open a web UI in a Termix tab or its own desktop window
- Connect directly, or over an SSH tunnel through the host
- Embedded pages never see your Termix login
- A web UI panel beside the SSH terminal and a dashboard card to open any web UI
Web Endpoint opens a host's web UI inside Termix: Proxmox, a router page, Portainer, Home Assistant, anything with a web interface. Open it in a Termix tab, or in its own window in the desktop app. Reach it directly, or over an SSH tunnel through the host when it isn't reachable otherwise.
It needs the Tunnels plugin.
Add an endpoint
- Open the host in Manage and turn on Enable web endpoints in its Web UI section.
- Press Add endpoint and fill in:
- Label, like
Proxmox. - Scheme, Port and Path, like
https,8006and/. - Access: Direct, or SSH tunnel.
- Open in: a Termix tab, or an Isolated desktop window in the desktop app.
- Label, like
- Save, then pick the endpoint from the host's menu.
Through Termix
Use Through Termix when your browser can't reach the host, for example when you open Termix from outside through a tunnel. The page opens in a new browser tab on its own temporary address, and every request goes through this server. Apps that expect to sit at the root of a site work, and so do WebSockets and logins. Nothing is rewritten, and pages stay apart from Termix and from each other.
It needs the Reverse Proxy plugin with a Web endpoint domain set: one wildcard DNS record, like *.apps.example.com, pointing at the proxy. See Reverse Proxy. Connect from Termix picks how the server reaches the host. Auto uses a tunnel when the host has SSH and connects directly when it does not. SSH tunnel and Direct force one or the other, like Direct for a firewall that has SSH on but serves its web UI to the server. Direct always needs an admin to turn on Let Termix reach hosts directly. It always opens in a browser tab, since a frame could not keep the app's login. The desktop app uses an SSH tunnel instead.
Beside the terminal and on the dashboard
A host with a web UI that opens inside Termix gets a Web UI panel beside its SSH terminal. Open it from the terminal edge or its tab menu, and pick the endpoint when the host has more than one. Turn it off for a host with Panel beside the terminal.
Add the Web UIs card in the dashboard's edit mode to open any of your web UIs in one click.
Direct or SSH tunnel
- Direct: your browser opens the host's address and port itself. The port has to be reachable from where you are.
- SSH tunnel: Termix forwards the port over the host's SSH connection. Use it for a web UI that only listens on the host itself, or behind a firewall. It needs SSH on for the host.
A tunnel always listens on 127.0.0.1 on the Termix server. In the browser, Termix serves it to you through its own address, behind your login, using a link that expires when you stop using it. The desktop app opens the tunnel directly.
Apps that load files from absolute paths like /static/app.js, or that need WebSockets, may not work through the browser. Use the desktop app for those.
Bind Host lets a tunnel listen on another address, but only when an admin turns on Allow tunnels on other addresses in the plugin's settings. Anyone who can reach that port then gets the web UI with no Termix login. Local Port is picked for you unless you set one.
Your Termix login stays safe
An embedded page never sees your Termix session. Embedded pages run in an isolated frame with their own cookies. If opening an endpoint would send your Termix cookies to it, because it is on the same hostname as Termix, Termix refuses and tells you why.
Some web UIs won't load in a frame, or loop on sign in because of how they set cookies. Use Open externally, or an Isolated desktop window in the desktop app, for those.
Allow invalid certificate accepts a self-signed certificate on a direct endpoint.