Troubleshooting problems with the bridge

About Article:

This article will describe how to debug the issues with the Virtuoso bridge.

Problem Statement:

Issues with the bridge functionality, such as connection failures, slow execution, and token misconfigurations, often arise from incorrect settings, network proxies, VPNs, or security software. Effective troubleshooting is essential to diagnose and resolve these problems promptly.

Solution:

Common causes of bridge issues:

1. Incorrect bridge/token set up
   • First check the bridge token is created with the token type “Bridge” in the desired environment (app2, production). If not, create the token in the correct environment.
2. Disconnected bridge
   • Restart the bridge instance.
3. Bridge updates in the default environment configured in Goal Settings

• Whenever there is a bridge update done in the default environment mapped to a Goal, for example - a new bridge was linked to the environment or the bridge was replaced or removed, the Goal setting needs to be refreshed
• This can be done by opening the Goal Setting and clicking on the “Save Changes” button
• If the “Save Changes” button is not enabled, refresh the page and then click on the “Save Changes” button.

4. Confirm there are no proxies (http or Socks). 
   • If there are, follow the steps mentioned here.
5. Make sure there's no VPN active that needs to be used, especially if you're operating a laptop outside the network and plan to use the Bridge. 
   • If there is, activate the VPN before starting the Bridge.

To generate and debugs the logs:

1. To generate bridge logs execute the following command in cmd/terminal 
   • bridge_client --token <REPLACE_with_your token> -o
2. To debug the bridge logs execute the following command in cmd/terminal
   • bridge_client --token “REPLACE_with_your token” -I DEBUG -n token_name
     
     

Reference material for Virtuoso Guide

• Bridge setup
• Quotas
• Troubleshooting