Prérequis système et réseau

Vérifiez que votre système et votre réseau répondent aux exigences minimales avant d'installer l’agent d'automatisation ACME de DigiCert.

Important

To avoid conflicts, do not install a DigiCert sensor and agent on the same system. Use a dedicated host for the sensor.

La configuration système requise

L'agent ACME fonctionne sur les systèmes Linux et Windows, avec les exigences suivantes :

Server type	Supported OS versions	Minimum specifications
Windows	Windows 10 Windows Server 2016 Windows Server 2019 Windows Server 2022 Windows Server 2025 Standard	Version 64 bits 2 Go de RAM (4 Go recommandés) 2 Go d’espace disque libre (minimum) Microsoft .NET Framework 4.x installed Administrator privileges
Linux	Red Hat Enterprise Linux 7.x Red Hat Enterprise Linux 8.x Red Hat Enterprise Linux 9.x Ubuntu 20.04 or later	Version 64 bits et paramètres régionaux des États-Unis requis 2 Go de RAM (4 Go recommandés) 2 Go d’espace disque libre (minimum) CLI utilities `awk`, `grep`, `sed`, `lsof`, and `dos2unix` installed Root privileges

Exigences réseau

The DigiCert agent on each host must be able to resolve the fully qualified domain names (FQDNs) for the local web server, either via DNS or a local "hosts" file.

Effectuer une connexion sortante en HTTPS (port 443).

Region	Platform URLs¹	TCP port	Protocol
Americas (U.S.A.)	`one.digicert.com`, `clientauth.one.digicert.com`	443	HTTPS
APJ (Japan)	`one.digicert.co.jp`, `clientauth.one.digicert.co.jp`	443	HTTPS
EMEA (Netherlands)	`one.nl.digicert.com`, `clientauth.one.nl.digicert.com`	443	HTTPS
EMEA (Switzerland)	`one.ch.digicert.com`, `clientauth.one.ch.digicert.com`	443	HTTPS
_{1. For users with an on-premises DigiCert ONE deployment, the agent needs to access port 443 (HTTPS) on the local DigiCert ONE instance and ClientAuth host (for example, my-org.one.digicert.com and my-org.clientauth.digicert.com).}

In addition, the agent requires outbound access to the below host for Trust Lifecycle Manager discovery and automation services:

Region	URL	TCP port	Protocol
All regions	`automation-service.digicert.com`¹	443	HTTPS
_{1. This service is delivered through a content distribution network (CDN) and the IP addresses may vary by region. If your organization uses IP-based allowlists, look up the automation-service.digicert.com host in your local region to determine which IP addresses to allow.}

Avis

If using a local DigiCert® sensor as proxy, the agent must also be able to connect outbound to the proxy listening port on the sensor. To learn more, see Use a sensor as a proxy server.

Loopback ports

To support automated certificate delivery, the agent binds to the following loopback port(s) on the local host. To adjust the loopback port numbers for an installed agent, edit the applicable configuration file/parameter in the agent conf sub-directory and restart the agent service.

Loopback port	Description	Agent conf file	Configuration parameter
58080	Local communications port for the plugin manager process used to manage certificate delivery events for Trust Lifecycle Manager.	config.toml	`ControlPort`
61613	Local communications port for Simple (or Streaming) Text Oriented Messaging Protocol (STOMP). Used for message queuing between the main agent process and the plugin manager process.	config.toml	`StompPort`

What's next

To install an agent on a single server, see: Install and activate a DigiCert agent.
To bulk install agents on multiple servers at once, see: Install DigiCert agents in silent mode.
If your organization has a private on-premises instance of DigiCert ONE, make sure you meet the additional requirements to use DigiCert agents for certificate lifecycle automation.