On Azure Marketplace, Xcalar Design (the browser-based UI) talks HTTPS protocol to the Xcalar instance (running on Azure) on the default port of 443.
For this test to be successful, these basic conditions must exist:
A network pathway to the target host (an Azure Virtual Machine) must exist
The target host must be up and running
Xcalar's web server on the target host must be up and running
Steps to test:
1) get the url from your portal page, it should look like this:
Next, double click on that link (or paste it into your Chrome browser address bar), and a successful call will result in a page that looks like this:
If you get a failure of some kind, it might look something like this:
Now it's time to do some quick diagnostic work.
Often, something like a firewall will be in play, so let's start with that.
First confirm that you can get to the basic Microsoft Azure Portal:
cut-and-paste these this command into a terminal window:
nc -vz portal.azure.com 443
This is what a successful test should look like:
If you do not have success, then there is a good chance that an internal policy or network configuration is a problem. You will need to work with your internal IT organization to diagnose and resolve.
If you do have success above, then the "ping" command at at o/s prompt can be useful.
To test with ping - In Chrome, highlight the section of the url on your customer portal AFTER the "https://" - it should look something like this:
Now open a command line window, and at the prompt type ping + a space + [paste the contents of the copied-url there] , for example:
The "zero packet" loss means that the ping was successful.
Here is an example of a failed ping:
The 100% packet loss indicates that the ping is unable to communicate.
If you are not able to ping, then chances are pretty good that something is blocking the network (often somewhere inside the network and security infrastructure at your organization).
Another possible someone has powered down Azure virtual machine for node 0 of the Xcalar instance on the azure (typically not performed/managed by Xcalar software or personnel).
If you are able to ping successfully, then next step is to test port 443 of the Xcalar instance specifically, to see if you can reach a running web server on that host.
The shell command to do that is
nc -vz [paste the contents of the copied-url there] 443
here is an example of the syntax:
nc -vz xdp-standard-d3z44np5mzmak.azure.xcalar.cloud 443
Here is a successful execution:
Here is an unsuccessful execution:
If you do not achieve success with test of port 443, then please confirm with your IT organization that you are not being blocked by internal policy or configuration, specifically:
If you do achieve success and you still cannot successfully browse to the Xcalar Design UI, then please contact Xcalar Technical Support.