Bosh Director fails with "Input not an X.509 certificate"
search cancel

Bosh Director fails with "Input not an X.509 certificate"

book

Article ID: 293855

calendar_today

Updated On:

Products

Operations Manager

Issue/Introduction

When attempting to Apply Changes against the BOSH Director, it fails with:
Agent responded with error: Action Failed get_task: Task result: 1 of 11 pre-start scripts failed. Failed Jobs: uaa.
Exit code 1

Looking at the pre-start logs for the UAA process on the director, it mentions:

keytool error: java.lang.Exception: Input not an X.509 certificate


Environment

Product Version: 2.10

Resolution

This is caused by a formatting error in the Bosh Director -> Security -> Trusted certificates. One common issue is with white spaces before/after the certificates in the chain.

Copy the certificate chain into a separate text editor, and verify that there are no spaces other issues with the certificates. Once resolved, copy the chain back into Bosh Director -> Security -> Trusted certificates