Canary Endpoints/Ports (version 24)

Knowledge Base / Version 24 / System Admin Duties / General

updated 2 wk ago
3replies

The following is a list of default ports that Canary uses for interoperability between remote Canary services and its clients. The endpoints that need opened are unique to each deployment and can be changed, if necessary, by navigating to the Endpoints screen of a particular service tile within the Canary Admin client.

Port Number	Service	Description
55310	Licensing	(gRPC API) used by remote Canary services needing to lease a license
55311	Licensing	(REST API) used to add or return licenses to and from Canary's License Portal
55273	Admin	(gRPC) allows Canary Admin clients to connect remotely
55351	Identity	(gRPC API) used by remote Canary services to handle user authorization
55353	Identity	(REST API) used to authenticate Canary clients with OpenID Connect
55282	Historian	(gRPC API) used to add the Historian to a remote Views service
55255	Receiver	(Net.TCP) allows anonymous connection from a remote Sender service. Only needed if using Collectors older than v24.
55256	Receiver	(Net.TCP) allows secure connection from a remote Sender service. Only needed if using Collectors older than v24.
55253	Sender	(HTTP) allows clients to write data using the web API to the Historian over an anonymous connection
55254	Sender	(HTTPS) allows clients to write data using the web API to the Historian over a secure connection
55291	Store and Forward	(gRPC API) used by Canary/3rd party clients to write data to the Historian
55293	Store and Forward	(HTTPS) allows 3rd party clients using the web API to write data to the Historian
55321	Views	(gRPC API) used by Canary/3rd party clients (including the Excel Add-in) to read data from the Historian
55236	Views	(HTTPS) allows 3rd party clients using the web API to read data from the Historian
55260	ODBC	(Net.TCP) allows ODBC client connections to the ODBC service
443	Axiom	(HTTPS) allows Axiom clients to connect to the Axiom service

- damon_vinciguerra.1
- 2 wk ago
- Reported - view
would it be possible to add a column indicating if the firewall rules need to be inbound or outbound from the perspective of the service? I think it’s mostly inbound, but some seem outbound .
- smason
  
  7 days ago
  
  Reported - view
  , the endpoints are what the services are listening on so they are all inbound in that regard. Now, an outbound port may need opened for a service initiating the connection if they are being blocked, but typically outbound traffic is not as restricted. For example, the SaF service on a collector machine will use the same port number (55291) to send data to the SaF service on the HIstorian machine. Likewise, the Historian listens on 55282 for incoming Views services trying to connect. So it may be that the outbound port (55282) on the Views machine needs opened.
- damon_vinciguerra.1
  
  7 days ago
  
  Reported - view
  OK, all the service/port combos are listening. That makes sense. Thanks!