You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/troubleshooting.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,8 +29,9 @@
29
29
- Run `okdev ssh --setup-key` at least once per key pair.
30
30
- If local bind conflicts occur, use `okdev ssh --local-port <port>`.
31
31
- Verify the managed entry exists in `~/.ssh/config`: `Host okdev-<session>`.
32
-
- For tmux-enabled sessions, use interactive TTY mode: `okdev ssh` or `ssh -tt okdev-<session>`.
33
-
- To bypass tmux for one connection, use `okdev ssh --no-tmux`.
32
+
- For tmux-enabled sessions, use interactive TTY mode with `okdev ssh`.
33
+
-`ssh okdev-<session>` opens a plain shell by default.
34
+
- To bypass tmux for one `okdev ssh` connection, use `okdev ssh --no-tmux`.
34
35
- For unstable links, increase `spec.ssh.keepAliveIntervalSeconds` and `spec.ssh.keepAliveTimeoutSeconds`.
35
36
- If `ssh okdev-<session>` exits after a long stall, inspect `~/.okdev/logs/okdev.log` for proxy health events such as port-forward degradation or idle watchdog disconnects.
36
37
- Managed proxy sessions are designed to fail closed and return control to the local terminal rather than hang indefinitely on a dead port-forward.
0 commit comments