Knowledge Base / Version 21 / System Admin Duties / General

Canary Endpoints (version 21)

updated 2 yrs ago

The following is a list of the default endpoints that Canary uses for its services. The endpoints that need opened are unique to each deployment and can be changed if needed using the Canary Admin. Highlighted endpoints are enabled by default.

Admin

55273 - (Net.TCP - secure) allows remote connections from other Canary Admin clients

Historian

55281 - (gRPC - anonymous) allows an anonymous connection from a Views client machine
55283 - (gRPC - secure) allows a secure connection from a Views client machine

These endpoints only need to be enabled if trying to add a Remote Historian view to a Views service.

Receiver

55256 - (Net.TCP - secure) allows a secure connection from incoming Sender clients
55255 - (Net.TCP - anonymous) allows an anonymous connection from incoming Sender Clients

The Sender service will attempt to connect to the anonymous endpoint first, if enabled, then the secure endpoint.

Sender

55257 - (Net.TCP - Windows) - allows 3rd party application collectors to write data to the historian. This endpoint must be enabled if wishing to use the 'Data Entry' control in Axiom.
55254 - (HTTPS - secure Web API) - allows clients using the web API to write data to the historian using a secure connection
55253 - (HTTP - anonymous Web API) - allows clients using the web API to write data to the historian using an anonymous connection

Views

55234 - (Net.TCP - secure) allows internal clients, such as Axiom or the Excel Add-in, to connect securely and consume data from the historian
55231 - (Net.TCP - anonymous) allows internal clients, such as Axiom or the Excel Add-in, to connect anonymously and consume data from the historian
55236 - (HTTPS - secure Web API) allows clients using the web API to read data from the historian using a secure connection
55235 - (HTTP - anonymous Web API) allows clients using the web API to read data from the historian using anonymous connection