Common Issues and Errors in Integration with Pulse

This page provides a comprehensive guide to help you troubleshoot common issues and errors encountered during the integration with Pulse and the installation of agents. Whether you're facing connectivity problems, configuration errors, or unexpected behavior, this guide offers practical solutions to resolve them efficiently. Use the sections below to identify and fix the most frequent challenges.

SSL_ERROR_SYSCALL

You are using curl, wget or other ways to download the agent as a JAR file with the link provided to you from the Integration Wizard, and receiving this error:

curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to api.pulse.support:443

This error typically occurs when there are firewall or network connection issues. The SSL_ERROR_SYSCALL indicates that the SSL handshake failed, most likely due to a firewall or network policy blocking the request.

Solution

1. Check Firewall Rules: Ensure that your firewall is not blocking outbound connections to api.pulse.support on port 443. Update the rules if necessary to allow this traffic.

2. Verify Network Policies: Confirm that there are no network policies or proxies in place that might be interfering with the connection. If such policies exist, work with your network administrator to whitelist the required domain and port.

3. Test Connectivity: Use tools like ping or traceroute to verify that the server api.pulse.support is reachable from your environment.

4. Retry the Command: Once the network issues are resolved, retry the curl command to proceed with the agent installation.

If the issue persists after addressing these points, consider reaching out to your network administrator or Pulse support for further assistance.