LogoLogo
Open a Support Ticket!GridPlus.ioDiscordLattice Manager
  • Welcome!
  • Setup
    • Lattice1 Device Setup
  • Lattice1
    • Lattice1 Introduction
    • Lattice1 Security Features
      • Lattice1 Random Number Generation
    • How the Lattice1 Makes Transactions Readable with ABI Decoding
      • Advanced ABI Decoding
    • How to Manage Your Seed Phrase
    • Lattice1 Power Supply
    • Supported Digital Assets
    • Lattice1 WiFi Troubleshooting
    • Lattice1 Firmware Reference
    • Lattice1 Guides 🛠️
      • Update the Firmware
      • Verify That Your Lattice1 Is Authentic
      • View the Seed Phrase on Your Lattice and SafeCard
      • Claim Your "Verified Lattice1 Owner" POAP and Discord Role
      • Establish a Connection With Your Lattice1 via SSH
      • Connect to WiFi Using SSH
      • Disable Wifi When Connected via Ethernet Using SSH
      • Managing ETH Validator Keys
  • SafeCards
    • Introduction to SafeCards
    • Setting up a New SafeCard
    • SafeCard Operations
    • Lattice1 Doesn't Recognize the Inserted SafeCard
    • SafeCard CLI
  • Apps & Integrations
    • Lattice Manager
      • Managing Your Bitcoin Wallet
      • Creating Custom Address Tags
      • Using the Wallet Explorer
      • Connecting Your Lattice to Your Own Private Endpoint
      • Lattice Manager Troubleshooting
      • How to View the XPUB of Your Bitcoin Wallet
    • MetaMask
      • Installing MetaMask
      • Connecting to MetaMask
      • Advanced MetaMask Setup
      • MetaMask Troubleshooting
    • NuFi
      • Connecting to NuFi
    • Frame
      • Installing Frame
      • Connecting to Frame
      • Advanced Frame Setup
    • Rabby
      • Connecting to Rabby
      • Rabby Troubleshooting
    • MyCrypto
      • Connecting to MyCrypto
      • MyCrypto Troubleshooting
    • Ambire Wallet
      • Connecting to Ambire
    • Eidoo App (Mobile)
  • Additional Resources
    • Payment, Shipping, Delivery
    • GridPlus Affiliate Program
    • Developer Resources
    • GridPlus Brand Assets
    • Bug Bounty & Responsible Disclosure Policy
  • Blockchain Basics
    • Introduction
    • Wallets
    • A Brief Introduction to Private Keys
    • Blocks & Consensus Mechanism
    • UTXO vs. Account Model
    • Bitcoin
    • Ethereum
      • Smart Contracts
      • ERC-20 tokens
      • NFTs
      • Layer 2s
Powered by GitBook
On this page
  1. Lattice1
  2. Lattice1 Guides 🛠️

Establish a Connection With Your Lattice1 via SSH

PreviousClaim Your "Verified Lattice1 Owner" POAP and Discord RoleNextConnect to WiFi Using SSH

Last updated 1 year ago

Before you start, make sure your Lattice1 is connected to your router either through WiFi or Ethernet. Also, make sure you can communicate with your router through your computer.

If you want to change any network configuration or run software on your Lattice's router chip, which is a very lightweight Linux environment, you can SSH into your device using the following steps:

  1. On your Lattice screen, go to System Preferences → Device Info.

  2. The parameters you will want to use are "SSH Host" and "SSH Password".

  3. Open a terminal on your computer and type this SSH command: ssh root@<SSH Host>.local (just what you see under SSH Host without the <> marks)

  4. If this is your first time, it will ask you add the RSA key. Type yes and hit enter.

  5. You will be asked for the password - type in the <SSH Password> from your Lattice1 screen. Again, only the password itself, not the <> marks. Please note you might not see your input on this step, but type the password in and hit enter and you should be okay.

  6. If successful, you will see a welcome prompt with Lattice1 ASCII art and information about the GCE version. This is how the whole process should look on your terminal:

Done, you can now control your Lattice’s Linux environment: update configurations, run whatever software you want, or just poke around under the hood.

Troubleshooting

If you can't ping the Lattice1 through your router, your router is probably not configured for mDNS - the protocol that allows devices to broadcast their hostname on the local router network and for the router to rebroadcast it to other devices - which allows you to search for devices with the '.local' suffix.

To solve this, please check your router's user manual and look for enabling mDNS.

You can still communicate with the device even without mDNS enabled, but you will have to use the device's IP address instead of the hostname - so the command ssh root@GridPlus-xyz123.localwould becomessh root@123.456.789.012.

But if you’re looking for your private keys, !

you’ll be out of luck