Skip to content

Support

Narrow the connection. Keep the secrets out.

Most SSH problems can be diagnosed from the connection stage, server behavior, and app version without sharing credentials or private terminal output.

Contact support

Describe the expected result, what happened, the app version, device type, authentication method without its secret, and the last connection stage that succeeded.

Email 8BitsTerm support

Cannot connect

  • Confirm the host and port are reachable from the current network.
  • Verify the username and authentication method.
  • Review the host-key prompt carefully rather than accepting an unexpected identity.
  • Never send passwords, private keys, or complete private host information to support.

Port knocking

Confirm the configured knock sequence, transport, timing, and final SSH port match the server. Verify the knock independently at the server before changing authentication settings.

Colors, glyphs, or tmux look wrong

Include the remote terminal type, shell, multiplexer, and a sanitized example. Nerd Font or special glyph output also depends on the characters emitted by the remote program.

Command Recall or captures

Confirm the expected host and session. Avoid sharing captured output that contains credentials, tokens, customer data, internal addresses, or private command arguments.

Privacy and purchases

Read the Privacy Policy and manage Privacy Choices. 8BitsTerm uses Apple’s standard EULA.