Overview
This guide explains the available methods for accessing local or internal URLs on TestGrid devices. These methods help establish secure access to internal applications, APIs, staging environments, and enterprise systems.
Prerequisites
Before configuring access to internal URLs, ensure the following:
Access to the TestGrid portal is available.
Required network permissions and credentials are available.
Internal applications or services are accessible within your local network.
Steps
Method 1: TG Connect
TG Connect establishes a secure tunnel between your local/internal network and TestGrid cloud devices, allowing access to private applications.
Setup Instructions
Connect the devices to a network that has access to the internal URL.
Authenticate using your TestGrid credentials.
Run the following command to establish a tunnel:
tg-connect --token YOUR_AUTH_TOKEN
Once connected, access your local/internal URLs from TestGrid devices using the mapped address.
Method 2: VPN Configuration
Configure TestGrid devices to connect to your corporate VPN, enabling direct access to internal applications.
Setup Instructions
Ensure your VPN allows third-party device connections.
Obtain VPN credentials and configuration files.
Example:
.ovpn file for OpenVPN
Install the VPN client on TestGrid devices if supported, or route traffic through an enterprise VPN gateway.
Verify connectivity by accessing an internal URL.
Method 3: Proxy Setup
Configure a proxy server to route traffic from TestGrid devices through your local/internal network.
Setup Instructions
Set up a proxy server in your internal network.
Examples:
Squid
HAProxy
Configure TestGrid devices to use the proxy by updating network settings.
For SOCKS Proxy, use dynamic port forwarding.
Example:
ssh -D
Verify that traffic is routed through the proxy.
Method 4: Reverse Proxy (NGROK, Cloudflare Tunnel, etc.)
A reverse proxy exposes local applications securely to the internet, providing a temporary public URL mapped to an internal service.
Setup Instructions
Install NGROK or Cloudflare Tunnel.
For macOS:
brew install ngrok
For Windows:
choco install ngrok
Authenticate with your NGROK or Cloudflare account.
Start a tunnel to your internal service:
ngrok http 8080
Use the generated public URL to access the service from TestGrid devices.
Method 5: On-Premise TestGrid Setup
Deploy TestGrid within your internal infrastructure to ensure all test activities remain within your network.
Setup Instructions
Contact TestGrid support for an on-premise deployment package.
Caption: Request on-premise deployment package
Set up the TestGrid server within your internal environment.
Caption: Configure on-premise TestGrid environment
Connect TestGrid devices to the local infrastructure.
Caption: Connect devices to internal infrastructure
Ensure internal services are accessible without external tunneling.
Caption: Verify internal service accessibility
Use Case
Highly regulated environments with strict data security policies.
Large-scale enterprise testing within a private network.
Summary
| Method | Security | Ease of Use | Best For |
|---|---|---|---|
| TG Connect | High | Easy | Securely accessing internal URLs |
| VPN | High | Moderate | Enterprise-level internal access |
| Proxy | Medium | Moderate | Controlled traffic routing |
| Reverse Proxy | Low | Easy | Quick external access to local apps |
| On-Premise | High | Complex | Fully private infrastructure |
Troubleshooting
Connection Issues
Ensure firewalls or security settings allow traffic.Authentication Problems
Verify credentials and tokens.Performance Issues
Optimize network bandwidth and minimize latency.
Outcome
After completing the required setup:
Internal URLs can be accessed securely from TestGrid devices.
Applications, APIs, and staging environments can be tested successfully.
Network access can be configured based on organizational security requirements.
Still have a question?
Support Contact:
support@testgrid.io
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article