Common issues and solutions for Orb.
Error:
Error: dial tcp [::1]:8080: connect: connection refused
Causes:
- Relay server not running
- Wrong relay address
- Firewall blocking connection
- Network unavailable
Solutions:
-
Verify relay is running:
curl -I http://localhost:8080 # Should return HTTP response -
Check relay address:
# Ensure protocol and port are correct ws://localhost:8080 # Correct wss://localhost:8080 # TLS version http://localhost:8080 # Wrong (HTTP, not WebSocket)
-
Test with local relay:
# Terminal 1: Start relay orb relay # Terminal 2: Try connection orb connect --session <ID> --passcode <CODE> --relay ws://localhost:8080
-
Check firewall:
# Linux sudo ufw allow 8080 # macOS # System Preferences → Security → Firewall # Windows # Windows Defender Firewall → Allow an app
Error:
Error: session not found
Causes:
- Wrong session ID
- Session expired (>24h)
- Session never created
- Typo in credentials
Solutions:
-
Verify session ID:
# Double-check session ID from sharer # It's case-sensitive: abc123 ≠ ABC123
-
Check session age:
# Sessions expire after 24 hours # Ask sharer to create new session
-
Create fresh session:
# Sharer creates new session orb share ~/files # Note new credentials
Error:
Error: authentication failed
Error: handshake failed
Causes:
- Incorrect passcode
- Passcode has extra spaces
- Wrong key derivation
- Crypto mismatch
Solutions:
-
Verify passcode exactly:
# Passcode is case-sensitive # Check for spaces: "pass code" vs "passcode" # Copy-paste to avoid typos
-
Request credentials again:
# Ask sharer to resend passcode # Use secure channel
-
Create new session:
# If passcode lost/wrong, start over orb share ~/files # New credentials
Error:
Error: context deadline exceeded
Error: handshake timeout
Causes:
- Network latency
- Sharer not connected
- Firewall blocking packets
- Relay issues
Solutions:
-
Verify sharer is connected:
# Check sharer terminal shows: # "Waiting for connection..."
-
Test network speed:
ping -c 5 relay.example.com # Check latency -
Use closer relay:
# Self-host relay geographically closer # Or use relay with better connectivity
-
Try again:
# Temporary network issue # Simply retry connection
Error:
Error: permission denied
Causes:
- No read access to directory
- Files owned by different user
- SELinux/AppArmor blocking
Solutions:
-
Check permissions:
ls -la /path/to/share # Ensure files are readable -
Fix permissions:
chmod -R +r /path/to/share # Make all files readable -
Run as correct user:
# If files owned by different user sudo -u owner orb share /path/to/files
Error:
Error: directory does not exist
Causes:
- Typo in path
- Directory moved/deleted
- Relative vs absolute path
Solutions:
-
Verify path:
ls /path/to/directory # Confirm exists -
Use absolute path:
# Instead of: orb share ../files orb share /home/user/files -
Check current directory:
pwd # Verify you're where you think you are
Error:
Error: failed to initialize browser
Causes:
- Terminal not supported
- TTY not available
- Connection failed before launch
Solutions:
-
Use supported terminal:
- iTerm2 (macOS)
- Terminal.app (macOS)
- Windows Terminal
- Alacritty
- GNOME Terminal
- Dumb terminal
- Non-interactive shell
-
Check TTY:
tty # Should output /dev/pts/0 or similar # Not "not a tty"
-
Verify connection:
# Ensure handshake completed # Check connection logs
Error:
Error: download failed
Causes:
- Disk full
- Permission denied (local)
- Network interruption
- File locked on sharer side
Solutions:
-
Check disk space:
df -h . # Ensure enough space
-
Check write permissions:
ls -la . # Ensure current directory is writable
-
Change download location:
cd ~/Downloads orb connect --session <ID> --passcode <CODE>
-
Try smaller file first:
# Test with small file # If works, issue is large file handling
Symptoms:
- Garbled text
- Broken boxes
- Missing characters
- Weird colors
Causes:
- Terminal encoding wrong
- Unicode not supported
- Terminal too small
- Color scheme issues
Solutions:
-
Set UTF-8 encoding:
export LC_ALL=en_US.UTF-8 export LANG=en_US.UTF-8
-
Resize terminal:
# Minimum 80x24 # Recommended 120x30
-
Reset terminal:
reset # Clear any corruption -
Try different terminal:
# Use modern terminal emulator # Enable UTF-8 support
Error:
Error: build failed
Causes:
- Go version too old
- Missing dependencies
- Network issues downloading modules
- Platform not supported
Solutions:
-
Check Go version:
go version # Need Go 1.21 or higher -
Update dependencies:
go mod tidy go mod download
-
Clear cache:
go clean -cache go clean -modcache
-
Build with verbose output:
go build -v -x # See detailed build steps
Error:
bash: orb: command not found
Causes:
- Binary not in PATH
- Binary name incorrect
- Wrong directory
Solutions:
-
Check binary location:
which orb # If empty, not in PATH -
Run with full path:
/usr/local/bin/orb --version ./orb --version
-
Add to PATH:
export PATH=$PATH:/path/to/orb # Or copy to /usr/local/bin
Symptoms:
- Directory loading takes forever
- Browser appears frozen
Causes:
- Large directory (thousands of files)
- Network latency
- Slow disk on sharer side
Solutions:
-
Wait for completion:
# Large directories take time # Be patient
-
Share smaller directory:
# Instead of sharing entire home: orb share ~/specific-project
-
Check network:
ping -c 10 relay.example.com # Look for packet loss
Symptoms:
- File download takes very long
- Much slower than expected
Causes:
- Network bandwidth limited
- Large file size
- Relay bottleneck
- Encryption overhead
Solutions:
-
Check network speed:
# Run speed test # Compare to expected bandwidth
-
Use local relay:
# If over internet, use local relay # Reduces hops
-
Compress files:
# Sharer compresses before sharing tar -czf archive.tar.gz files/ orb share .
-
Split large files:
# Split large files split -b 100M largefile.dat part- # Download parts separately
Error:
Error: address already in use
Causes:
- Port 8080 already used
- Another orb relay running
- Other service using port
Solutions:
-
Check port usage:
# Linux/macOS lsof -i :8080 netstat -an | grep 8080 # Windows netstat -ano | findstr :8080
-
Kill conflicting process:
# Find PID from above kill <PID>
-
Use different port:
orb relay --port 9090
Symptoms:
- Relay exits unexpectedly
- Connections drop
Causes:
- Out of memory
- Too many connections
- Bug in code
- System resource limits
Solutions:
-
Check logs:
# Look for error messages # Check system logs
-
Increase limits:
# Linux ulimit -n 4096 # File descriptors
-
Restart relay:
orb relay --port 8080
-
Monitor resources:
# Watch memory/CPU top htop
Issue: Antivirus blocks Orb
Solution:
1. Add orb.exe to exclusions
2. Windows Defender → Virus & threat protection
3. Add exclusion for orb.exe
Issue: WebSocket connection fails
Solution:
# Check Windows Firewall
New-NetFirewallRule -DisplayName "Orb" -Direction Inbound -Port 8080 -Protocol TCP -Action AllowIssue: "orb" cannot be opened because the developer cannot be verified
Solution:
# Remove quarantine
xattr -d com.apple.quarantine orb
# Or allow in System Preferences
# Security & Privacy → Open AnywayIssue: Permission denied
Solution:
# Make executable
chmod +x orb
# Move to /usr/local/bin
sudo mv orb /usr/local/bin/Issue: SELinux blocks connections
Solution:
# Temporarily disable
sudo setenforce 0
# Or create policy
# Check audit logs for denialsIssue: systemd service won't start
Solution:
# Check status
systemctl status orb-relay
# View logs
journalctl -u orb-relay -f
# Test manually first
/usr/local/bin/orb relay# Version
orb --version
# System info
uname -a # Linux/macOS
systeminfo # Windows
# Network
ip addr # Linux
ifconfig # macOS
ipconfig # Windowsexport ORB_DEBUG=1
orb share ~/files
# More detailed outputWhen reporting bugs, include:
- Orb version (
orb --version) - Operating system and version
- Command that failed
- Complete error message
- Steps to reproduce
- GitHub Issues: Report bugs
- Discussions: Ask questions
- Documentation: Check this guide
- Examples: See usage examples
| Error | Meaning | Solution |
|---|---|---|
connection refused |
Relay not reachable | Check relay running |
session not found |
Invalid/expired session | Create new session |
authentication failed |
Wrong passcode | Verify credentials |
permission denied |
No file access | Check permissions |
address in use |
Port already used | Use different port |
handshake timeout |
Handshake didn't complete | Check network |
context deadline exceeded |
Operation timed out | Retry or check network |