Tessera can’t generate or import RSA keys: the current SSH stack can only offer the deprecated RSA/SHA-1 signature. Generate an Ed25519 key instead — every modern OpenSSH server accepts it. RSA keys left over from older versions are shown disabled.
mosh-server installed on the server?The iOS sandbox can’t bind ports below 1024 — pick a higher local port. Local ports also can’t repeat within one host. See port forwarding.
With transport mosh and custom launch mode there is no SSH connection to carry forwards. Switch the launch mode to auto-tmux or named tmux — those keep an SSH side channel that forwarding rides on.
Environment variables and startup snippets only run when the tmux session
starts. Kill the session on the server (tmux kill-session) and reconnect.
The files bridge is a separate SSH connection with the same trust rules. Open a terminal session to the host, review the Unknown Host sheet, and accept the key — then reopen the panel.
Directory following needs OSC 7 from your shell. Use the panel’s Enable
follow — install shell integration button, then exec $SHELL or reconnect.
Details in files.
The connection is fine but large bursts of output never arrive — an MTU mismatch on WSL2’s virtual adapter, swallowing every big packet. See WSL MTU stalls.
iPadOS gates LAN access behind the Local Network permission. If you denied it, re-enable it in the Settings app under Tessera.
Check the iOS notification permission (the bell settings sheet deep-links to it). Remember that background delivery is best-effort: iPadOS may suspend long background sessions. See notifications.
They’re present in the interface but not wired up yet.
Capture a diagnostics log (settings → diagnostics → export log) and file an issue at GitHub Issues. The log is redacted and only leaves your device when you share it.