[BUG] no tmux monitor over tailscale ssh

[termix-github-bot]

Platform

Website

Version

2.5.1

The Problem

tmux monitoring works fine for direct login/connections, but if using tailscale ssh as login method a message is shown:

Could not connect to the host. Check that it is online and reachable.

How to Reproduce

1. Connect via tailscale ssh
2. Open a tmux session
3. Open tmux monitor in termix

---

Note

Submitted via the Termix Discord Support Bot
Reported by xyzulu.bb on Discord
View Discord thread

[termix-triage-bot]

Auto-triage

When connecting via Tailscale SSH, the tmux monitor's pane preview fails to connect, displaying an error that the host is unreachable. This occurs because the preview attempts to establish a new terminal transport instead of reusing the existing Tailscale-backed connection.

Field	Value
Type	Bug
Difficulty	3/5 (Moderate)
Priority	Urgent
Labels	bug ssh platform-web

A maintainer will review shortly. If the auto-classification looks wrong, feel free to say so.

[xyzulu]

I traced this in the Termix codebase and this appears to be an architecture/transport mismatch, not a tmux bug itself. I'm going to see if I can provide a PR to simply use the tailscale auth (if applicable) for tmux-monitor. We'll see.

Summary

When using Tailscale SSH auth, tmux monitor can list/manipulate sessions, but the pane preview/attach terminal may fail with:

Could not connect to the host. Check that it is online and reachable.

This happens because tmux monitor preview creates a new terminal transport/session (new instance identity), rather than reusing an already-established Tailscale-backed transport.

---

What works vs what fails

Works

• tmux monitor backend endpoints for session/window/pane data and actions (overview/focus/split/kill/etc.).
• These are host-executed operations and do not require the exact same attach flow as interactive terminal preview.

Fails

• Pane preview attach path inside tmux monitor.
• This path instantiates a new Terminal with a generated instanceId, effectively creating a fresh connection path that can fail under Tailscale SSH semantics.

---

Evidence in code

1) Pane preview intentionally creates a per-mount PTY / fresh instance

src/ui/features/tmux-monitor/PanePreview.tsx

• Comment in file states one PTY per mount.
• instanceIdRef is generated with newInstanceId().
• Reattach explicitly creates another new instance ID.

That means preview is not transport-reuse by design; it’s a fresh terminal identity.

2) Terminal host config is rebuilt from host fields

In the same component, Terminal is passed:

• ...host
• sshPort: host.port
• instanceId: instanceIdRef.current
• tmuxAttachSession: pane.sessionName

This is a host-based connect path, not an attach-to-existing-session path.

3) Backend session manager is tab/instance aware

src/backend/hosts/terminal/session-manager.ts

Attach logic checks tabInstanceId and handles conflicts/takeover behavior for different instance IDs.
So a newly generated instance is treated as a separate attach context, which aligns with “new connection path”.

4) Tailscale is a distinct auth type, but this path still uses generic host-based connect semantics

src/types/index.ts includes authType: "tailscale", but tmux preview path still reconstructs standard terminal host config instead of explicitly reusing an existing Tailscale transport/session.

---

Why this reproduces exactly as reported

• Direct SSH: generic host-based new attach path works.
• Tailscale SSH: initial login transport works, but tmux preview’s secondary connection path can fail “reachable” checks/connection assumptions.
• Result: monitor can partially function, but preview attach throws host unreachable.

---

Impact

• Affects hosts using Tailscale SSH auth in tmux monitor preview/attach.
• User-facing behavior is confusing because some monitor actions work while preview fails.
• Not likely a host availability problem; likely transport selection mismatch.

---

Recommended engineering direction (for maintainers)

1. Transport reuse first in tmux monitor preview:

   • Prefer attach to existing terminal transport/session identity when available.
   • Avoid ad-hoc new instance creation for Tailscale mode.

2. Auth-aware attach strategy:

   • If authType === tailscale, do not require generic host reachability preflight before attach.
   • Route via established Tailscale-aware transport path.

3. Reattach behavior:

   • For Tailscale hosts, rebind/recover existing session first; full reconnect as fallback only.

4. Regression matrix:

   • Direct SSH + preview attach
   • Tailscale SSH + preview attach
   • Tailscale with no direct TCP 22 exposure
   • MagicDNS-only naming cases

---

[xyzulu]

This can be closed now the PR is merged.

[termix-triage-bot]

It looks like this issue may be resolved based on the comments.

Based on the thread, the fix was: The issue was resolved by a pull request that addressed the architecture/transport mismatch, allowing tmux monitor pane previews to work correctly with Tailscale SSH.

If that's correct, feel free to close it. If the problem is still happening, please drop a comment with your current Termix version and any new info.