Skip to Content
Remote AccessSSH Access

SSH Access

Direct SSH access to the host device is available for advanced debugging scenarios.

We recommend accessing running Docker containers through the cloud IDE terminal instead of SSH-ing into the host device. Direct host access breaks the principle of isolated, containerized environments.

Prerequisites

  • The device must be reachable on the local network (or via a VPN)
  • You need the device’s private key from the .flock configuration file
  • Password authentication is disabled by default for security

Extract the SSH Key

The private key is embedded in the .flock device configuration file. Extract it:

cat /path/to/mydevice.flock | jq -r .authentication.key > id_rsa

Set the correct file permissions:

chmod 600 id_rsa

Connect via SSH

ssh -i id_rsa {project_owner}@{device_ip}

The SSH username must be the project owner’s name in lowercase.

When to Use SSH

SSH access is appropriate for:

  • Diagnosing OS-level issues (networking, disk, kernel)
  • Inspecting Docker daemon state
  • Recovering from failed updates
  • Accessing hardware peripherals not mounted in containers

For debugging your app, use the cloud IDE’s side-menu terminal instead — it connects directly to your running container without SSH.

Last updated on
Host AccessLoRaWAN Sensors