Before proceeding with a Connect install, it is a good idea to perform a health check and verify a few things.
Linux & Windows Pre-Installation Checklist
Ensure server meets the minimum System Requirements
Perform cURL command against needed endpoints to see if they are reachable from the customer network. These include:
https://c3.acr.org/health (C3 Healthcheck)
https://activate-connect.acr.org/health (device code proxy)
Verify the server can resolve itself in DNS
1 nslookup <servername>- Ports used by Connect Windows
To avoid port conflicts and smooth running of Connect Windows on the host, please ensure these ports are not used by any other software
| 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-9100 | 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 Imaging Service | 5005 | No |
| DICOM Anonymization Service | 5006 | No |
| Master Id Index Service | 5007 | No |
| MariaDB | 3306 | No |
| RabbitMQ | 5672 | No |
For Connect Linux, Docker maintains an internal docker network and is not exposed at the host level so there are no dedicated ports for each service.
Additional Linux Specific Pre-Installation Steps
Verify the Nvidia container runtime worked with the cuda docker image
1sudo docker run --rm --gpus all nvidia/cuda:11.0-base nvidia-smi