Remote Access
Remote Access lets you use Terminay terminals from another browser on the same network or through the HTTPS origin you configure.
Start And Stop
Open the Remote menu in the app header. Choose Start Server to turn Remote Access on, or Stop Server to turn it off. You can also open Remote Access Settings and use Pair Device or Stop Remote Access.
Pair A Browser
Choose Start Server & Show QR or Show Pairing QR. Scan the QR code from your phone, or copy the pairing link and open it in another browser. Pairing links expire; show the QR again to generate a fresh one.
If Terminay shows multiple addresses under Connect To or Available Addresses, choose the one your other device can reach. On many local networks that address begins with 192. or 10..
Use The Remote Browser App
In the remote browser app, enter a device name, scan or paste the pairing link, then select Pair Device. After pairing, the browser remembers this host.
The remote app shows your projects and terminal sessions as tabs. Select a session to attach to it, type normally, and use Focus, Clear, Reset, Settings, or Disconnect from the top menu. On touch devices, Terminay adds quick keys for Ctrl, Alt, Escape, Tab, arrows, paging, zoom, and common control shortcuts.
Remote sessions mirror active Terminay terminals. If there are no terminals running, the browser app shows No active sessions. Closed sessions disappear, and exited sessions are marked as exited.
Manage Trust And Activity
Use Remote Access Settings to manage devices and connections.
- Paired Devices shows saved browsers, when they were added, and when they were last seen. Use Revoke to remove access.
- Active Connections shows connected browsers and how many sessions each has attached. Use Close to disconnect one.
- Recent Audit Log shows recent events such as pairing, authentication, connection open/close, device revocation, and connection revocation.
Origin, Binding, And TLS
Remote Access requires HTTPS. By default, Terminay uses https://localhost:9443, binds to 0.0.0.0, and generates a self-signed certificate if TLS paths are blank.
In Settings > Remote Access > Host & Origin, set the exact HTTPS origin browsers should use, such as https://terminay.example.com. The origin must start with https:// and must not include a path, query, or fragment.
Set Bind address to the local interface Terminay should listen on. In TLS, leave the certificate and key paths blank for an auto-generated self-signed certificate, or provide PEM certificate and private key paths.
Security And Troubleshooting
Only pair browsers you trust. Anyone with an active paired browser can interact with your terminal sessions. Revoke lost or shared devices, close suspicious active connections, and stop the server when you do not need remote access.
A self-signed certificate may show a browser warning. Use your own trusted certificate for a smoother remote setup. If pairing or authentication fails, check that the browser is opening the same HTTPS origin shown in Terminay, that the QR/link has not expired, that the selected address is reachable, and that your firewall allows the configured port.