Before proceeding with the ACR Connect install, it is a good idea to perform a health check and verify a few things.
Our Pre-Installation script will also check all requirements automatically. This can be downloaded HERE
Pre-Installation Checklist
Ensure server meets the minimum System Requirements
Ensure that these URLs are reachable from the customer network:
https://c3.acr.org/health (C3 Healthcheck)
https://activate-connect.acr.org/health (device code proxy)
Ports Used by ACR Connect
To avoid port conflicts and ensure ACR Connect functions correctly, please ensure the ports below are not used by any other application:
| Service | Host Port(s) | Firewall Access Needed |
| Gateway Service | 443 | Inbound to the server (Local LAN only) Outbound to specific sites listed above |
| Gateway Service | 80 | No |
| DICOM Service | 9090 | Inbound to the server (Local LAN only) |
| DICOM Listener | 104 (Default but Configurable) | Inbound to the server (Local LAN only) |
| Kestrel Static | 5000 | No |
| Homepage Service | 5001 | No |
| Data Manager Service | 5002 | No |
| DICOM Service | 5003 | No |
| Event Logger Service | 5004 | No |
| DICOM Anonymization Service | 5006 | No |
| Master Id Index Service | 5007 | No |
| MariaDB | 3306 | No |
| RabbitMQ | 5672 | No |
Certificate
An SSL certificate, in PFX format, is used to create a secure web connection between the server where ACR Connect is installed and the end user. The certificate can be a self-sign certificate, or one provided by a CA. If one is not available, it can be created as part of the installation.