-
Notifications
You must be signed in to change notification settings - Fork 21
Connection examples
Urls may be HTTP or HTTPS. Hosts can be referenced in numerous ways, IP address, localhost, FQDN etc. You can use any available inbound port number that is not already in use. If using 443, a connection will not require the port number. Here are some examples. Yes means connection schema is supported. No, means that URL connection will likely fail (not work).
| Connection URL | Insights in Enterprise | Insights Desktop |
|---|---|---|
| http://localhost:9999 | no | yes |
| https://localhost:9999 | no | no |
| http://computer1:9999 | no | yes |
| https://computer1:9999 | no | no |
| http://12.120.95.153:9999 | no | yes |
| https://12.120.95.153:9999 | yes | no |
| http://computer1.esri.com:9999 | no | yes |
| https://computer1.esri.com:9999 | yes | no 1 |
1 Insights Desktop can make connections to HTTPS Kernel Gateway endpoints, if the Kernel Gateway uses a domain or a certificate authority certificate.
2 If using port 443, the connection url will look like this https://computer1.esri.com. Here computer1 is the machine name.
Note: Please open the url in the browser and bypass the exceptions before using it to connect in the Insights application. Please refer to the exceptions wiki here
Get Started
Connecting to the Kernel
General Features
Deployment Patterns
Frequently asked questions