Remote Hive Setup
Learn how to connect remote machines to your rbee colony.
Critical Configuration
Remote hives MUST use Queen’s public IP address, not localhost.
This is the #1 cause of “worker not found” errors.
The Problem
When you spawn a remote hive, workers need to know WHERE to send heartbeats.
❌ What Goes Wrong
bash
# Remote hive spawned with localhost queen URLssh remote-machine "rbee-hive --queen-url http://localhost:7833"Result:
- ❌ Worker sends heartbeat to
localhost(its own machine!) - ❌ Queen never receives heartbeat
- ❌ Queen thinks worker is offline
- ❌ Inference requests fail with “no worker available”
✅ The Solution
bash
# Remote hive spawned with Queen's public IPssh remote-machine "rbee-hive --queen-url http://192.168.1.100:7833"Result:
- ✅ Worker sends heartbeat to Queen’s IP
- ✅ Queen receives heartbeat
- ✅ Worker appears in registry
- ✅ Inference works
Queen Configuration
Step 1: Find Your Queen’s IP Address
bash
# On the machine running Queenip addr show | grep "inet " | grep -v "127.0.0.1"Output
inet 192.168.1.100/24 brd 192.168.1.255 scope global eth0
Your Queen’s IP is 192.168.1.100.
Step 2: Configure Queen’s Public Address
File: ~/.config/rbee/config.toml
~/.config/rbee/config.toml
[queen]port = 7833public_address = "192.168.1.100" # ← Your Queen's IP
# OR use hostname# public_hostname = "queen.local"For local-only setups (single machine), you can omit public_address.
It defaults to localhost.
Step 3: Restart Queen
bash
# Restart Queen to apply configrbee queen stoprbee queen startRemote Hive Setup
Prerequisites
- SSH access to remote machine
- Queen’s public IP configured
- Firewall allows port 7833
Step 1: Install rbee on Remote Machine
bash
# SSH into remote machinessh user@192.168.1.101
# Install rbeecurl -sSL https://install.rbee.dev | shStep 2: Start Hive with Queen URL
bash
# On remote machinerbee-hive --queen-url http://192.168.1.100:7833The hive will automatically register with Queen and start sending heartbeats.
Step 3: Verify Registration
bash
# On Queen machine, check registered hivescurl http://localhost:7833/v1/jobs \-H "Content-Type: application/json" \-d '{"operation": "status"}'You should see your remote hive in the output.
Troubleshooting
Multi-Machine Example
Architecture
┌─────────────────────────────────────────┐
│ Main Server (192.168.1.100) │
│ - Queen (port 7833) │
│ - rbee-keeper (GUI) │
└─────────────────────────────────────────┘
↓ Heartbeats
┌──────┴──────┬──────────────┐
│ │ │
┌───▼────┐ ┌────▼─────┐ ┌────▼─────┐
│Gaming │ │ Mac M3 │ │ Server │
│PC │ │ │ │ │
│GPU 0,1 │ │ Metal │ │ CPU only │
└────────┘ └──────────┘ └──────────┘
192.168.1.101 .102 .103Configuration
Queen (192.168.1.100):
~/.config/rbee/config.toml
[queen]port = 7833public_address = "192.168.1.100"Gaming PC (192.168.1.101):
bash
rbee-hive --queen-url http://192.168.1.100:7833Mac M3 (192.168.1.102):
bash
rbee-hive --queen-url http://192.168.1.100:7833Server (192.168.1.103):
bash
rbee-hive --queen-url http://192.168.1.100:7833