How to Resolve TG Connect Authentication Failures

Modified on Sun, Jun 21 at 1:36 AM

Overview

This guide helps diagnose and resolve TG Connect authentication failures caused by proxy restrictions, firewall rules, or network-related issues.


Prerequisites

Before troubleshooting, ensure the following:

  • TG Connect is installed.

  • Internet connectivity is available.

  • Terminal or Command Prompt access is available.

  • The TG Connect authentication token is available.


Steps

Step 1: Verify Port 22 Access

  1. Confirm whether the client network allows TG Connect traffic on Port 22.

Verify

  • TG Connect works only on Port 22.

  • If Port 22 is blocked, the tunnel will not work.


Step 2: Verify Authentication Endpoint Accessibility

The following error indicates that the authentication endpoint is not reachable:

An error occurred while making the API request for authentication

Step 3: Verify Token Authentication

Before establishing the tunnel, TG Connect first authenticates the token.

If token authentication fails, the tunnel connection will not proceed.

Run the following command:

curl -v --location 'https://poc7.testgrid.io/api/vpn-tunnel-authentication-public' --form 'token="test"'

Step 4: Identify Network or Proxy Blocking

If the user receives errors similar to the following:

Recv failure: Connection was reset SSL/TLS connection failed curl: (35)

Interpretation

  • Proxy configuration may be blocking the authentication endpoint.

  • SSL/TLS inspection may be interfering with the connection.


Step 5: Verify Proxy and Firewall Configuration

Ask the client or network team to verify the following:

  • The proxy allows HTTPS tunneling using the CONNECT method to poc7.testgrid.io:443

  • The proxy is not intercepting or terminating TLS traffic

  • No firewall is blocking the domain IP 128.136.25.172

  • No transparent or SSL-intercepting proxy is configured for this domain

Verify

Once the curl command works successfully, TG Connect authentication should also work successfully.


Outcome

After completing these troubleshooting steps:

  • TG Connect authentication issues can be identified.

  • Proxy and firewall restrictions can be validated.

  • Authentication endpoint accessibility can be confirmed.


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

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article