Network requirements
The qbee-agent
is designed to operate reliably across a variety of network environments — including those with restricted or monitored internet access. For the agent to function correctly, specific hosts must be reachable to enable core services like configuration management, inventory reporting, metrics, logs, and remote access.
All communication is conducted securely over port 443 (TCP) using HTTPS/TLS. Devices must be able to resolve DNS and establish outbound connections to the relevant service endpoints listed below.
Core Platform Communication
All qbee-agent versions require access to the following endpoint to send and receive:
- Configuration updates
- Device inventory
- Logs and metrics
- Other management-related data
Primary endpoint:
device.app.qbee.io
- IP addresses:
34.255.133.233
54.72.39.215
99.81.8.44
- IP addresses:
DNS and firewall configuration
Ensure your firewall or network policy allows outbound connections to device.app.qbee.io
on port 443, and that DNS resolution is not blocked or redirected.
Remote Access Requirements
Remote access uses different endpoints depending on the version of the qbee-agent.
For agent versions ≤ 2024.05
- Endpoint:
rcnsl-1.app.qbee.io
- IP address:
99.80.24.171
This was the legacy remote access endpoint used for agents up to and including version 2024.05
.
For agent versions ≥ 2024.06
- Endpoint:
edge.app.qbee.io
- IP addresses:
3.33.204.188
15.197.248.71
This is the new remote access infrastructure introduced in version 2024.06
, which supports improved scalability and reliability.
Which endpoint does my device need?
Make sure to use the correct remote access endpoint based on your agent version. You can check your agent version using:
qbee-agent --version
Summary
To ensure smooth and secure operation of qbee-agent
, your device must be able to:
- Resolve DNS
- Connect over TCP port 443 to:
device.app.qbee.io
for core platform servicesrcnsl-1.app.qbee.io
(if agent ≤ 2024.05)edge.app.qbee.io
(if agent ≥ 2024.06)
If you're running devices behind a firewall or proxy, make sure these addresses are explicitly allowed.
If you have any questions about networking setup or encounter connectivity issues, please reach out to support.