ggLeap and ggRock Network Communication Requirements

This article aims to provide network communication requirements for cloud-hosted ggCircuit services

Outbound IPs

Fastly: ggLeap API runs through Fastly, requiring their outbound IPs for API access. These IPs change periodically, so subscribing to updates is recommended.

IP list: https://api.fastly.com/public-ip-list

AWS: Add AWS IP ranges for SQS (tcp/443) and API gateway (tcp/443) to enable ggLeap client-to-backend communication (non-API).

IP list: https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html

Note:Addresses listed for API_GATEWAY are egress-only; no specific subset exists for SQS or API Gateway ingress.

Cloudflare: Alow Cloudflare IP ranges.

IP list: https://www.cloudflare.com/ips/

Extracting IP Ranges with PowerShell

Use these PowerShell commands to extract IP ranges from the AWS JSON file:

Install the AWS Tools module:

   Install-Module -Name AWS.Tools.Common

Get and filter IPv4 IP prefixes:

   Get-AWSPublicIpAddressRange | where {$_.IpAddressFormat -eq "Ipv4"} | select IpPrefix

Note:This outputs a list of IPv4 IP prefixes for configuring your network firewall or security group rules.

Additional Considerations

Firewall/Security Groups: Ensure your firewall or security group rules allow both inbound and outbound traffic to/from the specified IP ranges on the necessary ports (primarily tcp/443).
Regular Updates: IPs in these lists change periodically. Implement a process to keep these updated in your network configuration.
Testing: After making changes, thoroughly test your ggLeap and ggRock setup to ensure proper communication and functionality.

ggRock Server Network Requirements

For ggRock server updates and core functionality, the following URLs must be accessible:

Package Repositories:

ggRock Application:

Recommendation:To ensure seamless operation and future compatibility, it is strongly recommended to whitelist all https://*.ggleap.com and https://.ggcircuit.com, and https://.ggrock.com` URLs. This will accommodate potential new subdomains used for future features.

Note:ggRock servers do not directly access AWS services.

Troubleshooting ggLeap after a network interruption

An unforeseen interruption—even a brief network flicker—can break communication between the Web Admin and client PCs and cause clients to enter offline or fake admin mode. If ggLeap remains stuck after login, or a machine appears offline even though Windows has internet access:

Check the local network, ISP connection, and network equipment. Restart the router, switch, or other network gear, then test again. If possible, test using another ISP; an issue affecting only one location or branch is likely local.
On the affected PC, enter Admin mode and open Command Prompt. Run ping 8.8.8.8 to verify connectivity, and capture the result for troubleshooting.
Restart the affected PC. This is the preferred way to relaunch ggLeap after Admin mode and allows it to start in shell mode. You can alternatively sign out of Windows with Ctrl + Alt + Del and sign back in.
If the issue affects multiple PCs, reboot the server and test again. For a single affected PC, swap its network cable with the cable from a working PC to help isolate a local cable or machine issue.
If login remains stuck, update one PC using the latest Alpha installer at https://download.ggleap.com/alpha, confirm the version number on the login screen, and test before applying the update to other PCs.
Ensure firewalls and security groups allow client access to the required ggLeap services, primarily over TCP/443. See the client URLs below.

ggLeap Client Network Requirements

ggLeap clients require access to the following URLs:

Third-Party Integrations:

Kidas:

Note:Additional Kidas URLs may be required. Consult Kidas documentation for the most up-to-date information.

Salad:

Note:Refer to the official Salad support article for detailed network requirements:https://support.salad.com/article/186-how-to-unblock-salad-with-your-isp

Important Note:In addition to the URLs listed above, clients will also require access to the URLs necessary for launching and running games and applications.These requirements vary depending on the specific applications being used and should be addressed separately.Consult the documentation for each game or application for its specific network requirements.

Updated on: 10/11/2026

Was this article helpful?

Thank you!