What to do if a Groundplex node is unable to register to the control plane

CHECKPOINT : Is there a proxy between the groundplex node and the Control Plane?

Outbound connectivity to the Control Plane can be tested using the following curl command:

On Linux JCCs,

$ curl -v https://elastic.snaplogic.com:443

On Windows JCCs,

C:\curl -v https://elastic.snaplogic.com:443

NOTE: The curl command is not typically available on Windows servers. If necessary, a third-party Windows-specific version can be dowloaded here.

If there is a proxy involved, the groundplex node must be configured to be proxy-aware as documented here.

CHECKPOINT: Is the groundplex node able to communicate to the Control Plane?

The groundplex node must be able to communicate with the SnapLogic Control Plane from within the customer’s network. For a full list of requirements for a groundplex node, please refer to our product documentation here.

Outbound connectivity from the groundplex node to the Control Plane can be verified using the telnet command:

On Linux JCCs,

$ telnet elastic.snaplogic.com 443

On Windows JCCs,

C:\telnet elastic.snaplogic.com 443

NOTE: The telnet command is not typically available by default on Windows servers. If it is not available, follow the instructions here.

In the event of a telnet test failure, consult the troubleshooting guide here.

CHECKPOINT: Is the groundplex node configured correctly?

The groundplex node must be configured with the correct values in the keys.properties and global.properties files. The SnapLogic DevOps team is responsible for provisioning groundplexes and providing a configuration cheat sheet to provide the customer.

The groundplex node must configured to utilize a supported JRE version to function correctly. Configuration specifics for Windows JCCs are available here.