Problem
| Info |
|---|
| The Appliance Server is not communicating with the Cloud |
...
- Open the Cloud UI and go to Settings (on the left hand side) / Discovery / Appliances
- Look at the list of Appliance Servers. If your Appliance Server is listed there and has a green bar under 'Last Status' then it is communicating correctly with the cloud.
Solution
Check the Appliance Server
...
| Info | ||||
|---|---|---|---|---|
| ||||
To verify a port is available on a host:
For example:
|
Verify Connectivity Across the WebSocket
The ws connection used to communicate over the WebSocket is also a HTTPS http connection.
To verify that change the protocol to https and add the live-data endpoint, then use curl to connect. For example:
| Code Block |
|---|
curl -sI https://<host>:443/communication/live-data |
On production this is:
| Code Block |
|---|
curl -vsI https://hostiqcloud.iquate.net:443/communication/live-data |
If not, typically a 403 Forbidden response, indicates that the routes are not open. (Ask DevOps to resolve)
If this responds with a 500 2xx or 5xx error, then communication is okay. Otherwise the route is not available (probably because of firewalls)
(If the WebSocket URL is ws, then use a http connection)
In the Beta environment the Appliance Server public IP address needs to be whitelisted. (see /wiki/spaces/HADM/pages/1511969 for instructions)
Logs Required for Troubleshooting
On the Appliance Server
First, get the logs from the websocket in docker.
| Code Block |
|---|
docker logs communication_websocket-client_1 > /opt/iqas/server-4.5/log/websocket.log
docker logs communication_rabbitmq-appliance_1 > /opt/iqas/server-4.5/log/rabbitmq.log |
Then take all the logs in the /opt/iqas/server-4.5/logs directory.
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...