When upgrading JetPatch connectors in environments utilizing JetProxy or where endpoints rely on public DNS names that don't directly map to the JetPatch server's private IP, connectors may become disconnected. This issue arises because the connectors might attempt to communicate using an internal-only address, rendering them 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:
-
Update Connector URLs:
-
For Linux Endpoints:
- Manually edit the connector's configuration file to update the core server URL (see instructions).
- Utilize the
modify_csclient_core_url.shscript (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:
- Manually edit the connector's configuration file to update the core server URL
- (see instructions).
-
For Linux Endpoints:
-
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.
-
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.
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.
Comments
0 comments
Please sign in to leave a comment.