Network Requirements for the Evolo Gateway

Network and Security Requirements for Evolo Gateway

Written By Evolo Support

Last updated 3 days ago

In order for the Evolo Gateway to communicate with the Evolo platform and receive updates, the following ports and domains must be open for outbound traffic.

The required domains depend on the installation type.

Standard installation

This applies to installations where the gateway is managed via Balena

Domain	Protocol	Port	Purpose
*.balena-cloud.com	TCP	443	Balena Cloud communication, VPN tunnel, and updates
hub.evolo.no	TCP	443	Communication with the Evolo platform
app.evolo.no	TCP	443	Access to the application

Custom Docker setup

This applies to installations where the Evolo Gateway is run directly with Docker Compose.

Domain	Protocol	Port	Purpose
registry. evolo.no	TCP	443	Docker Registry for downloading and updating Evolo Gateway
hub.evolo.no	TCP	443	Communication with the Evolo platform
app. evolo.no	TCP	443	Access to the application

On-premises installations

For on-premise installations without full internet access, the following domains must be open for Evolo to be updated. Alternatively, updates can be transferred manually via file/FTP systems.

Domain	Protocol	Port	Purpose
registry-1.docker.io	TCP	443	Docker registry.
auth.docker.io	TCP	443	Docker authentication.
download.docker.com	TCP	443	Downloading and updating Docker packages.
hub.docker.com	TCP	443	Docker Hub.
production.cloudflare.docker.com	TCP	443	Docker content delivery.
production.cloudfront.docker.com	TCP	443	Docker content delivery.

Common requirements

This applies to all installation types. DNS and time synchronization must be available for the gateway to communicate reliably with the necessary services.

Domain	Protocol	Port	Purpose
—	UDP	123	Time synchronization. Not required for the Internet if local NTP is provided via DHCP
—	UDP	53	DNS lookup. Not required for the Internet if local DNS is provided via DHCP

Summary

Always open TCP 443 to the domains applicable to the selected installation type.
Open UDP 123 and UDP 53 if the gateway does not receive NTP/DNS via DHCP.
For custom Docker Compose setups, registry.evolo.no is required to download and update the Evolo Gateway.
On-premises installations require access to Docker’s domains for updates, unless updates are handled manually.