Overview

This article provides troubleshooting guidance for resolving JetPatch connector disconnections that occur during upgrades in environments using JetProxy or DNS-mapped configurations. 

These disconnections happen when connectors attempt to communicate using internal-only addresses that are unreachable from external endpoints.

Common Causes

JetProxy Environments

In setups with JetProxy, the internal manager URL (private IP or hostname) can differ from the external URL. 

If the connector is configured with an internal-only address, it will attempt to connect to an address that external endpoints cannot reach.

Public DNS Mappings

Endpoints configured to use public DNS names that don't resolve to the JetPatch server's private IP due to network configurations can lead to connectivity issues.

Resolution Steps

Step 1: Update Connector URLs

For Linux Endpoints

• Manually edit the connector's configuration file to update the core server URL (see instructions).
• Utilize the script (see attached) to update the connector's core server URL. 
• This script allows you to set the correct primary and secondary URLs for the connector.

For Windows Endpoints

Step 2: Deploy Updated Connector Management Service

After updating the URLs, deploy a new connector management service with the accurate primary and secondary URLs to the affected endpoints.

Step 3: Verify Connectivity

• Ensure that the endpoints can reach the JetPatch server using the updated URLs.
• Check firewall settings and network configurations to confirm that communication is permitted.

Conclusion

By following these steps, you can resolve connector disconnection issues in JetProxy environments or setups where public DNS names don't map directly to the JetPatch server's private IP.