Issue: Service does not start with signed assemblies. - Issue: Service does not start with signed assemblies. - Conductor Platform - Foundation 24.1 - Foundation 24.1 - Ready - Hyland RPA - external - Hyland-RPA/Conductor-Platform/Foundation-24.1/Hyland-RPA-Conductor-Platform/Troubleshooting/Issue-Service-does-not-start-with-signed-assemblies. - 2025-04-03

Solution: In some rare cases, our signed assemblies are blocked due to Firewall restrictions and therefore the service is unable to start without any detailed exception. In this case, it would be required to either unblock the required URLs used by the Certificate authorities or to adjust the Conductor.exe.config to allow the service to start.

Conductor config:

<configuration> 
   <runtime> 
      <generatePublisherEvidenceenabled="false"/> 
   </runtime> 
</configuration>

Firewall restrictions:

crl.globalsign.com. CNAME 21600 global.prd.cdn.globalsign.com.
global.prd.cdn.globalsign.com. CNAME 900 cdn.globalsigncdn.com.cdn.cloudflare.net.
cdn.globalsigncdn.com.cdn.cloudflare.net. A 300 104.18.21.226
cdn.globalsigncdn.com.cdn.cloudflare.net. A 300 104.18.20.226
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
tl.symcb.com. CNAME 300 crl-symcprod.digicert.com.
crl-symcprod.digicert.com. CNAME 3600 cs9.wac.phicdn.net.
cs9.wac.phicdn.net. A 3600 93.184.220.29