How to Access Internal URLs Using VPN on TestGrid Devices

Overview

This guide explains the available options for accessing local or internal URLs on TestGrid devices using VPN applications, network-level VPN configurations, proxy setups, tunneling solutions, and cloud-hosted environments.

Prerequisites

Before configuring access to internal URLs, ensure the following:

• Access to the required TestGrid devices is available.

• VPN credentials or network configuration details are available.

• Internal applications or URLs are accessible within the client network.

Steps

Method 1: Client VPN App Installation on TestGrid Devices

Description

If the client provides a VPN app, it can be installed on TestGrid devices to establish a secure connection to the internal network.

Implementation Steps

1. Install the client VPN application on the required TestGrid devices.

2. Configure the VPN settings based on the client instructions.

3. Ensure the VPN connection remains active during testing.

Challenges

• Some VPN applications require manual authentication for every session.

• Background VPN connections may disconnect if the application is closed.

Method 2: VPN Configuration at the Network Level

Description

Establish a VPN tunnel between the TestGrid network and the client internal network.

Implementation Steps

1. Coordinate with the client IT team to set up a site-to-site VPN.

2. Ensure required firewall rules and network configurations are completed.

Pros

• No need to install VPN applications on individual devices.

• Provides seamless access to internal resources.

Cons

• Requires security approvals and configuration from both environments.

• May require static IP whitelisting.

Method 3: Proxy Configuration on Devices

Configure a proxy on TestGrid devices to route traffic through the internal network.

Implementation Steps

1. Configure a proxy manually in the device Wi-Fi settings.

2. Alternatively, use a proxy application to route traffic through the internal network.

Pros

• Allows access to internal URLs without VPN dependencies.

Cons

• Some applications may bypass system proxy settings.

Method 4: Tunneling Solutions (Ngrok, Localtunnel, etc.)

Description

Expose internal URLs securely using tunneling solutions such as Ngrok or Localtunnel.

Implementation Steps

1. Run a tunneling tool on the local machine.

Caption: Start tunneling service

2. Generate a public URL mapped to the internal environment.

Caption: Generate public access URL

3. Use the generated URL on TestGrid devices for testing.

Caption: Access internal URL through tunnel

Pros

• Quick setup without modifying TestGrid devices.

Cons

• Security concerns may require additional authentication.

• Free plans may have bandwidth or speed limitations.

Method 5: Hosting a Temporary Server on a Public Cloud

Deploy internal services to a temporary public cloud server for external accessibility.

Implementation Steps

1. Host the application on a cloud platform.

Examples:

• AWS

• Azure

• GCP

2. Configure secure access for the hosted application.

Pros

• No VPN or tunneling configuration required.

Cons

• Requires cloud infrastructure setup.

• Requires additional security configuration.

Recommendation

The recommended method depends on the client infrastructure and security requirements.

• Use a client VPN application if an existing VPN solution is available.

• Use network-level VPN configuration for enterprise-level access.

• Use proxy or tunneling solutions for quick setup scenarios.

• Use cloud hosting if public access is acceptable.

Outcome

After completing the setup:

• Internal URLs can be accessed securely on TestGrid devices.

• Applications and environments can be tested successfully.

• Connectivity can be configured based on client security requirements.

Still have a question?

Support Contact:
support@testgrid.io