Selenium script timeout on Azure Global Monitoring Point

Products

• AppNeta

Issue/Introduction

Selenium scripts fail to load and time out after approximately 90 seconds when running from an Azure Global Monitoring Point (GMP), despite working on local physical monitoring points ․​

 

"Resource was still loading when script timed out (91.2s load) [Milestone 1] open: timeout: Timed out receiving message from renderer"

Environment

AppNeta

Cause

Broadcom-hosted Global Monitoring Points (Azure GMP) are considered external resources ․ If the target internal URL is not explicitly permitted through the corporate firewall for external traffic, the renderer will time out waiting for the resource to load

Resolution

STEPS:

1. VERIFY EXTERNAL ACCESSIBILITY:

   Confirm if the resource is reachable from outside the corporate network ․
   Attempt to access the target URL from a standard external PC or non-corporate network ․
   If the URL is unreachable, the issue is likely network-level rather than application-specific ․

    

2. INSPECT FIREWALL RESTRICTIONS:
   Coordinate with the network security team to check for blocked traffic ․

   • Provide the network team with the target URL and the timeframe of the failures ․
     Specifically check for blocks originating from Azure/Broadcom GMP IP ranges to the internal OneClick or Web Server ․

    

3. UNBLOCK EXTERNAL RESOURCES: Ensure the firewall allows traffic from the Monitoring Point ․

   • Request the network team to whitelist or allow traffic from the external resource to the target server port (e.g., 9443) ․