Troubleshooting

Another SSH client works, but eShell reports Connection refused

Compare host, port, username and proxy/jump-host settings. A common mismatch is another client using 10022 while eShell still uses the default 22.

Read Connecting TCP: address:port in the connection log. A TCP refusal occurs before password authentication. Check the actual listening port. For a single SSH jump host, select its saved profile in the target session; the gateway must allow TCP forwarding. Generic SSH proxies remain unsupported.

A restored tab is blank or shows Reconnect

Startup restores descriptions without connecting automatically. In current builds, the first click on a restored tab or sidebar entry starts progress. An instance that already failed or was cancelled requires explicit Reconnect. If no progress appears, verify that the shortcut points to the updated executable.

A remembered password still prompts for login

Check whether the previous connection succeeded before saving, whether the same profile and configuration path are used, whether the password changed and whether private-key authentication is selected. A rejected saved password opens the dialog rather than retrying indefinitely.

First-time host verification is separate from password storage. See authentication.

Missing duplication or IP paste actions

Duplication belongs to the tab context menu; IP pasting belongs to the terminal content menu. Current builds put them at the top. Scroll inside long menus to reach more actions. Hold Shift while right-clicking when terminal mouse reporting is enabled.

Duplicate SSH Channel and IP pasting are disabled without a usable connection. Verify the running app version.

The local IP is not my public address

It is the actual local endpoint of the SSH TCP connection. VPN and LAN routes may use their own adapter addresses. This action does not query your public Internet address.

SSH works, but SFTP does not

Verify the SFTP subsystem and directory permissions on the server. Some minimal SSH servers provide only a shell. Read the transfer error instead of assuming the password failed.

Uploads reject existing remote names. After a network failure, check for temporary files as described in SFTP.

Document previews look different from Office

PDF uses native page rendering. Word and PowerPoint mainly extract text; Excel shows saved values. Use Enter on a file to open the system default app for full document fidelity.

Files does not follow cd

The root comes from the project or starting directory, not the shell's current directory. Verify the root after switching projects and refresh after filesystem changes. Update older builds that do not switch roots automatically.

The exe cannot be replaced, or the old interface remains

Exit the corresponding app, check the shortcut target and actual process path, then replace the whole runtime folder. Do not replace an arbitrary individual DLL from the package.

Alt+O does not open the session manager

Use an eShell build containing this shortcut fix, focus the terminal and press Alt+O. It opens the local SSH session manager and is not forwarded to the server, including in a shell, tmux/Claude or a detached terminal window. Close existing Settings, authentication or paste-confirmation dialogs before retrying. Older builds offer the manager in the + Session or SSH tab context menu.

Typing or echo feels delayed

Updated builds remove the per-command SSH input wait and the extra output repaint delay. Characters still use server echo, so network conditions and remote applications also affect response time. Cursor blinking does not hold text until the next blink.

Compare a plain shell with tmux/Claude on the same connection. Note differences during continuous typing, Backspace and window resizing. If only tmux/Claude is slow, report that scenario and the versions. If every scenario is slow, include VPN/proxy use and results from another client. Desktop responsiveness still needs manual testing; loopback timings do not establish real-server performance.

Report a problem

Include the app build, Windows version, DPI, steps, expected result and actual behavior. For SSH, provide connection stages and sanitized errors. Exclude passwords, keys, tokens and unrelated terminal output from screenshots. Use the source repository for feedback.