Use cases

Close port 22 on a VPS and still get a shell

Stop the brute-force noise: no inbound SSH at all, a shell and ssh through Fieldhand, every session logged.

For: people with a few VPSs or cloud VMs who'd rather not expose SSH.

With port 22 firewalled, the VPS's outbound connection is the only way in.VPSport 22 closedFieldhandrelay.fieldhand.devYoubrowser or sshoutbound :443browser or fh ssh
With port 22 firewalled, the VPS's outbound connection is the only way in.

Steps

  • Install the agent, open a shell from the dashboard and check it works.
  • Keep sshd listening on 127.0.0.1 only (ListenAddress 127.0.0.1), or close 22 in the provider's firewall. fh ssh user@vps still works, since it connects to the VPS's loopback through the agent.
  • Keep the provider's web console as your fallback if the agent is ever down.

What you get

  • No SSH port for scanners to find; nothing to rate-limit.
  • Each session in the audit log: who, when, from which address, how long.
  • Health and disk alerts for the same machines.

Good to know

  • Access then depends on your Fieldhand account: use a strong sign-in and limit teammates by tag. The trust model is in Security model.

Start

Create a workspace at fieldhand.dev (the first 5 devices are free, with every feature), click Add devices and run the command on the machine:

curl -fsSL https://api.fieldhand.dev/install.sh | sudo sh -s -- --token fhe_…

Or look around the live demo fleet first.

Something wrong or missing on this page? Tell us.