Nexus Repository 2 Remote Health Check Analysis fails with SSL errors


Visit for documentation on Nexus Repository version 2.

You are using Nexus Repository 2 OSS or Nexus Repository 2 Professional and have tried to Analyze a repository using Remote Healthcheck (RHC). This doesn't seem to work and you notice an error in the Nexus Repository log file similar to:

2014-03-03 10:57:08 WARN [pxpool-1-thread-8] admin org.sonatype.scheduling.DefaultScheduledTask - Exception in call method of scheduled task Health Check: central PKIX path building failed: unable to find valid certification path to requested target


Have you configured your Nexus Repository 2 to use a proxy server or is Nexus Repository behind a corporate firewall?

Most commonly this error happens when a proxy server rewrites the (Nexus Repository 2 Pro) or (Nexus Repository 2 OSS) a certificate with a custom one that Nexus Repository does not trust.


You can use Nexus Repository's built-in truststore to trust the remote certificate.

The following solution applies to the default central proxy repository shipped with Nexus Repository. However, these steps can be performed against any repository exhibiting this problem.

  1. Open Administration -> Capabilities
  2. Click New. Select SSL: Health Check. Click Add. Click Save.
  3. Open Administration -> SSL Certificates Click Add... -> Load From Server. Enter if using Nexus Repository 2 Pro, enter if using Nexus OSS. Then click Load Certificate, then Add Certificate after verifying the certificate displayed.
  4. Open Administration -> Scheduled Tasks. Find the Health Check: central scheduled task. Uncheck the Enabled checkbox and Save. Recheck the Enabled checkbox and Save. Click the Run button when the task is enabled and rerun the task.
Have more questions? Submit a request


  • 0
    Roy Lyons

    I would really like to script this so I can run it a couple of times a day since our environment employs an ssl interception.

    Is the way to do so by using the openssl command to obtain the PEM and then posting to /service/siesta/ssl/truststore with a payload of 


    "value" : "..."


    where "..." is the certificate content obtained from the openssl command?

    Is there any way to simply trust our root CA in the nexus built-in truststore so that any certificates that are signed by our CA will be automatically accepted?

  • 0
    Peter Lynch

    Hi Roy,

    First get the PEMs of the remote server, using your proxy server settings. This command prints the entire certificate chain. Replace localhost and 8888 with your proxy server host and port names.

    keytool -J-Dhttps.proxyHost=localhost -J-Dhttps.proxyPort=8888 -printcert -rfc -sslserver

    The output will print a PEM for each certificate in the chain - usually you want the last one, as this will likely be the proxy server CA certificate PEM. You can verify the last one is your proxy server by loading it in the Nexus UI and previewing it before adding it. Alternately examine the entire chain in detail by leaving off the -rfc option to keytool.

    BTW: You are describing the correct way to POST the PEM into the trust store.


  • 0
    Peter Lynch

    We are closing this article for comments.

    If you have a support license, please contact us by submitting a support ticket.

    If you do not have a support license, please use our Nexus Users List or our other free support resources.

Article is closed for comments.