...
This is normally caused due to security policies related to Firewalls, or other networking related security configurations that prevent access to the SeaLights API. In order to verify this is the case, try running a cURL command to your dashboard URL:
| Code Block |
|---|
curl -vI https://<YourCustomDNSName>.sealights.co |
| Tip |
|---|
...
|
...
| Code Block |
|---|
| curl -vI https://csdemo.sealights.co access the SeaLights API and there is no need for this document. |
If using a proxy, you should add the relevant parameter
| Code Block |
|---|
curl -vI https://<YourCustomDNSName>.sealights.co --proxy http://myproxy.mycompany.int |
| HTTP/2 200 code should be returned. If this code is received |
If you need a generic Sealights endpoint, you can
...
use the following command
| Code Block |
|---|
curl -vI https://csdemo.sealights.co |
| Warning |
|---|
In case this command fails, it is important to understand why. Looking at the detailed output (given by the |
| Info |
|---|
The above cURL command commands runs on native Linux. If using Windows, you will need to run it from a PowerShell prompt as it is allows |
...
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 custom domain Sealights dashboard URL only (https://<YourCustomDNSName>.sealights.co)
...