Project sync fails with unknown certificate authority error in Ansible Automation Platform 2.1

Solution Verified - Updated -


  • After installing a controller and a private automation hub with self-signed certificates, syncing a project that uses an execution environment stored on the private automation hub fails with an error similar to the following:

    Error: initializing source docker://<hub_fqdn>/ee-supported-rhel8:latest: pinging container registry <hub_fqdn>: Get "https://<hub_fqdn>/v2/": x509: certificate signed by unknown authority

    Where <hub_fqdn> is the fully-qualified domain name of the private automation hub. The error appears because the controller tries to pull the execution environment image associated with the project, and it fails to validate the self-signed server certificate used by the private automation hub.


  • Ansible Automation Platform 2.1
  • A private automation hub configured to use a self-signed x509 certificate.
  • A controller configured to use a self-signed x509 certificate.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content