The appliance not showing in the UI after deployment

Owned by Conor McCann
Last updated: Jan 12, 2023 by Andy Trayler
2 min read

Problem

  1. The customer has deployed the appliance and were able to successfully register the appliances on the CloudSphere website.

  2. The appliance is not visible in the UI

Solution

This problem is typically caused by a lack of communicationpath from teh appliance to the CAM SAAS platform. This can be tested from the appliance using the following command to check the communication health between the appliance and cloud.

curl -v https://api.<host>.cloudsphere.com/communication/health

The <host> value should be replaced with the appropriate target environment: iq1, iq2 or iq3

Successful call to the SAAS platform

iquate@lap-hpiqcloud-app02:~$ curl -v https://api.iqcloud.iquate.net/communication/health * Trying 99.83.165.242... * TCP_NODELAY set * Connected to api.iqcloud.iquate.net (99.83.165.242) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Client hello (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 * ALPN, server accepted to use h2 * Server certificate: * subject: OU=Domain Control Validated; OU=PositiveSSL Wildcard; CN=*.iqcloud.iquate.net * start date: Oct 3 00:00:00 2019 GMT * expire date: Oct 14 23:59:59 2021 GMT * subjectAltName: host "api.iqcloud.iquate.net" matched cert's "*.iqcloud.iquate.net" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x5628ca4eb4f0) > GET /communication/health HTTP/2 > Host: api.iqcloud.iquate.net > User-Agent: curl/7.58.0 > Accept: */* > * Connection state changed (MAX_CONCURRENT_STREAMS updated)! < HTTP/2 200 < date: Tue, 27 Jul 2021 21:29:07 GMT < content-length: 0 < x-request-time: 0 < x-correlation-id: c1475331-65cd-41e4-b0aa-8ef3cb5a4b8f < strict-transport-security: max-age=31536000; includeSubDomains; preload < content-security-policy: upgrade-insecure-requests < permissions-policy: geolocation=(self), midi=(), sync-xhr=(self), microphone=(), camera=(), magnetometer=(), gyroscope=(), fullscreen=(self), payment=() < referrer-policy: strict-origin < x-content-type-options: nosniff < x-frame-options: SAMEORIGIN < x-xss-protection: 1; mode=block < access-control-allow-origin: * < access-control-allow-credentials: true < * Connection #0 to host api.iqcloud.iquate.net left intact iquate@lap-hpiqcloud-app02:~$

Unsuccessful call to the SAAS platform

 

Â