Skip to main content

​
What you’ll need

  • A Compute instance created via the Hivenet dashboard
  • Your SSH private key
  • Windows Terminal or another SSH-capable terminal (like PowerShell)
  • A configured config file (optional but helpful)

​
Step 1 – Open the SSH connection details

Open your instance in Compute and go to Connectivity options → SSH. Compute exposes a stable SSH endpoint for the instance on port 22. The console shows the current hostname and connection command. Use those values rather than building the hostname yourself. Connect Instance Windows 1 Pn

​
Step 2 – Connect

Fastest option (recommended)
  1. In the dashboard go to Instance → Connectivity options → SSH.
  2. Click Copy to terminal to connect.
  3. Paste the command into your terminal and hit Enter.
    • The command already includes your instance ID and user.
    • It only works if you’ve added the “Add this to your SSH/config file” snippet shown right below the command.
Connect Instance Windows Gif Gi Build the command yourself If you prefer to type the command manually, use the hostname and username shown in the instance’s SSH connection details:
SSH uses port 22 by default, so you do not need to specify the port unless the console tells you otherwise. **If you’ve created a Host entry in **~/.ssh/config

​
Step 3 – Use a ProxyCommand if needed

Some connections require a jump host (a “bastion”) for access. If you’re getting timeouts, try this:
You may need to replace id_ed25519 if your key has a different name.
This creates a secure tunnel from your machine to the instance through Hivenet’s bastion.

​
Step 4 – Confirm your connection

If everything works, you’ll land in a Linux shell on your instance. You can now:
  • Install packages
  • Clone repos
  • Run workloads
  • Start your apps (like Fooocus, Jupyter, etc.)

​
Troubleshooting

  • Terminal closes immediately — Run your SSH command from an open terminal window instead of double-clicking a file.
  • Connection timed out — Add -v to get detailed output and check for network issues.
  • Permission denied — Check that your SSH key matches what you uploaded in the Compute dashboard.
  • Bad Gateway — You may be trying to access a web app before it’s started. Use curl localhost:<port> to confirm it’s running.