Support

There is no support desk and no ticket queue — this is a small open-source project, and everything happens in the open on GitHub. That has one real advantage: you can see whether your problem is already known before you write anything.

Bugs and feature requests

Open an issue. What helps most: what you were connecting to (the kind of server, not its address), what you expected, what happened, and your Chrome version. If the terminal printed an error, paste it — but check it for hostnames and usernames first, because the issue is public.

Abuse and privacy

Someone using our relay to reach your server, or a question about what we keep: abuse@sshterm.dev. For an abuse report, include the destination address and a timestamp with a time zone — the relay's journal is keyed by destination and time, and 30 days is as far back as it goes.

Answers to the three most likely questions

The icon disappeared after I installed it

Chrome hides new extensions behind the puzzle-piece icon in the toolbar. Click it, find SSH Terminal, and pin it — with pictures, here.

Can I avoid your relay?

Yes. The relay is part of the repository; run it on your own machine and point the extension at it in Settings → Relay. Sessions then never touch our infrastructure. Chrome cannot open a raw TCP socket from an extension, so some relay is unavoidable, but it does not have to be ours.

Does it work on a Chromebook or a locked-down work laptop?

That is the case it is built for. There is nothing to install beyond the extension itself, no native host, and no developer mode. If your organisation's policy blocks extensions outright, nothing here can get around that — and should not.