Overview¶
qbee-connect is a desktop application for managing secure remote access connections to Qbee.io-managed devices. It provides a graphical interface for browsing your device inventory, establishing port-forwarding connections, and managing multiple simultaneous tunnels — without manual SSH commands.
qbee-connect V2 is built with the Fyne UI framework and supports Windows, Linux, and macOS.
Key Features¶
- Device Browser — View and search your Qbee device inventory in a paginated table
- Port Forwarding — Configure TCP and UDP port forwarding to remote devices with a GUI
- Multiple Connections — Manage several simultaneous tunnels to different devices
- Account Switching — Switch between multiple Qbee tenant accounts
- System Tray — Run in the background with system tray integration
- Cross-Platform — Available for Windows, Linux, and macOS
Quick Start¶
Get connected to a remote device in under 5 minutes: Getting Started
How qbee-connect Works¶
qbee-connect establishes secure port-forwarding tunnels between your computer and remote Qbee devices through the Qbee platform. This architecture allows you to access services on remote devices without opening any inbound ports or configuring VPNs.
Tunnels & Port Forwarding¶
A tunnel forwards traffic from a local port on your computer to a remote port on a Qbee device. When you connect to localhost:<local-port>, your traffic is routed through the Qbee platform to the remote device's <remote-port>.
Your Computer (localhost:2222) → Qbee Platform (Tunnel Relay) → Remote Device (localhost:22)
Service Presets¶
qbee-connect includes service presets that pre-configure the remote port for common services:
| Service | Remote Port | Protocol |
|---|---|---|
| SSH | 22 | tcp |
| HTTP | 80 | tcp |
| HTTPS | 443 | tcp |
| VNC | 5900 | tcp |
| RDP | 3389 | tcp |
You can also configure custom ports for any service.
Key Properties¶
- No inbound ports required — You don't need to open any ports on your computer or the remote device. All connections are initiated outbound from qbee-connect.
- End-to-end encryption — Traffic is encrypted using HTTPS/TLS between your computer and the Qbee platform, and from the platform to your device.
- Firewall friendly — Since connections are outbound, qbee-connect works through most firewalls and NAT configurations without additional configuration.
- Protocol agnostic — While SSH is the most common use case, tunnels work with any TCP service (HTTP, databases, VNC, custom services).
Multiple Simultaneous Tunnels¶
You can establish multiple tunnels to multiple devices simultaneously. Each tunnel uses its own local port, and all connections remain active as long as qbee-connect is running. This allows you to:
- SSH to multiple devices at once
- Access web interfaces on multiple remote devices
- Run database queries against several remote databases
- Transfer files between devices
Why Use qbee-connect¶
Qbee provides three tools for remote device access: qbee-connect, qbee-cli, and the Qbee web UI. Each connects to the same Qbee platform but serves different workflows.
Feature Comparison¶
| Feature | qbee-connect | qbee-cli | Web UI |
|---|---|---|---|
| Interface | Desktop GUI | Command line | Browser |
| Device browsing | Visual table with search | CLI commands | Web dashboard |
| Port forwarding | GUI dialog with presets | CLI flags | No |
| Multiple connections | Multiple simultaneous | Multiple simultaneous | N/A |
| Account switching | In-app dropdown | Separate login | Account selector |
| System tray | Yes | No | No |
| Automation/scripting | No | Yes | No |
When to Use qbee-connect¶
Choose qbee-connect when:
- You prefer a graphical interface — Browse devices visually, configure connections through dialogs
- You manage multiple simultaneous connections — Track multiple tunnels in one window
- You work across multiple accounts — Switch accounts without re-authenticating
- You want background operation — Run in system tray while window is closed
Quick decision guide:
- Need port forwarding with a GUI? → qbee-connect
- Need port forwarding via command line or scripting? → qbee-cli
- Need remote console or agent management only? → Web UI
Example Use Cases¶
- System Administrator managing multiple devices — Keep SSH tunnels open to several servers while working
- Developer accessing remote services — Connect to web interfaces, databases, and debug ports with saved configurations
- Field technician with limited terminal experience — Use visual interface instead of memorizing CLI commands
- User working across multiple tenant accounts — Switch between development, staging, and production environments instantly
See Also¶
| Intent | Document |
|---|---|
| Getting Started | |
| Install qbee-connect and connect to your first device | Getting Started |
| Using qbee-connect | |
| Log in to qbee-connect | Managing the Application → Authentication |
| Switch between accounts | Managing the Application → Authentication |
| Use the system tray | Managing the Application → System Tray |
| Browse my devices | Devices & Connections → Finding Devices |
| Open a connection to a device | Devices & Connections → Creating Connections |
| Understanding | |
| Understand authentication | Security |
| Troubleshooting | |
| Troubleshoot a connection issue | Troubleshooting |