Network considerations
FlexxAgent, in its usual operation, requires a series of network requirements to connect to cloud orchestration services and support complex network ecosystems and proxies. Before proceeding with the deployment of the agent on devices, it is recommended to validate that at the network level they can access the defined destinations in required URLs and ports.
Regarding bandwidth usage, when FlexxAgent starts, it collects and sends an initial report of approximately 75 KB; from that point, it sends differential reports of approximately 3-4 KB. This process is responsible for executing on-demand or automatic actions on the device. At times when you are performing these actions, network traffic may increase.
FlexxAgent Analyzer collects user session information every 15 seconds, such as application consumption, resource usage, and more. And it adds this information in files of about 35-50 KB, which are sent every 5 minutes to the consoles.
In multi-user systems, a single instance of FlexxAgent will run and as many instances of FlexxAgent Analyzer as user sessions the system has.
Required URLs and Ports
In terms of communications, FlexxAgent must be able to contact the orchestration layer of the service hosted on the Internet, which includes:
| URL | Ambit | Port | Region | Product |
|---|---|---|---|---|
| queue***.servicebus.windows.net | Agent | 443 | West Europe | FXXOne, FlexxClient & FlexxDesktop |
| flxiothub***.azure-devices.net | Agent | 443 | West Europe | FXXOne, FlexxClient & FlexxDesktop |
| https://west-eu.agent-api.flexxanalyzer.com | Agent | 443 | West Europe | FXXOne, FlexxClient & FlexxDesktop |
| https://flexxibleglobal.blob.core.windows.net | Agent | 443 | West Europe | FXXOne, FlexxClient & FlexxDesktop |
| https://api.ipify.org | Agent | 443 | West Europe | FXXOne, FlexxClient & FlexxDesktop |
ras.flexxible.com (ra.flexxible.com will be deprecated in June 2025) | Agent – Remote Assistance | 443 | West Europe | FXXOne, FlexxClient & FlexxDesktop |
| https://update.workspaces.flexxible.com/ | Agent | 443 | West Europe | FXXOne, FlexxClient & FlexxDesktop |
| https://agents-weu.flexxible.com | Agent | 443 | West Europe | FlexxClient & FlexxDesktop |
| https://agents-weu.one.flexxible.com | Agent | 443 | West Europe | FXXOne |
| https://agents-weu.flexxible.net | Agent | 443 | West Europe | FXXOne, FlexxClient & FlexxDesktop |
*** unique identifier provided by Flexxible.
Deep SSL Inspection
Some security solutions include Deep SSL Inspection (deep SSL inspection) in cases where you use this functionality. Deep SSL Inspection should be disabled for the following URLs:
- https://flxsbname\*\*\*.servicebus.windows.net
- https://flxiothub\*\*\*.azure-devices.net
- https://agents-weu.flexxible.com
- https://agents-weu.flexxible.net
- https://ras.flexxible.com
Wake on LAN (WoL)
Wake on LAN allows devices to be powered on by sending a Magic packet that instructs the network card to power on. The following is required in order to use this functionality:
- Compatible network card
- Activate WoL in BIOS/UEFI
- Configure WoL in the operating system
- A
Bridgedevice on the same network as the device to be powered on, with FlexxAgent installed and reporting.
Normally, Wake on LAN works within a local network, being able to jump between subnets as long as no firewall or network device prevents the sending of the magic packet. If this is the case, in environments segmented into subnets, the network level exception should be configured to allow the addressing of the magic packet between subnets.