Agents Connectivity

Problem: My network contains security policies that prevent agents from reaching the SeaLights platform

This is normally caused due to security policies related to Firewalls, or other networking-related security configurations that prevent access to the SeaLights API. To verify this is the case, try running a cURL command (or equivalent) to your dashboard URL:

Linux (cURL)

curl -vI https://<YourCustomDNSName>.sealights.co

If using a proxy, you should add the relevant parameter -proxy http://myproxy.mycompany.int

PowerShell

Linux (wget)

HTTP/2 200 code should be returned. If this code is received, you can access the SeaLights API and there is no need for this document.

If this command fails, it is essential to understand the reason. Looking at the detailed output (given by the -vI flags) can point us in the right direction.

• If you need a generic Sealights endpoint, you can use https://connect.sealights.co in your command.

• If running on a Linux container without cURL, you can install it using apt-get update && apt-get install -y curl command or use the wget equivalent (see above).

Solution

If a firewall is present, it needs to allow network traffic to reach the SeaLights platform, and depending on your organization’s policy, you can use one of the following solutions.

Allow outbound traffic to Sealights' domain

The Firewall should allow outbound connections on port 443 (TLS v1.2) to our domain https://*.sealights.co. For a more restrictive rule, you can open the connections to your Sealights dashboard URL only.

Allow outbound traffic to Sealights' range of IP addresses

Sealights integrates with F5 Volterra. To ensure proper connectivity, configure your firewall or access control rules to allow traffic to and from the IP address 159.60.128.87, which serves as the central ingress point for all Sealights servers.

Related articles

• Java Keystore: Add Certificate

• Build Failure: SLF4J NoClassDefFoundError (Maven)

• JaCoCo Offline Instrumentation: No Coverage (Maven)