Closed hammy7867 closed 1 year ago
Hey!
I have not seen this error before, but some users on StackOverflow suggest it can be caused by:
-----BEGIN CERTIFICATE-----
and -----BEGIN [TYPE] PRIVATE KEY-----
)\r\n
and \n
as newlines.In case of the latter, the tool dos2unix
can probably help you out (scroll down to "Ready-to-run binaries" or "Distributions including this version of dos2unix" to download/install). Just run dos2unix <filename>
to convert it to a plain UTF8 file.
Let me know if that helps.
Joris
I'm closing this issue for now. Feel free to re-open if the problem still exists.
I am running the connect containers in AWS Fargate. I am putting the certificate and key on a shared volume. I have verified that the certificate is valid, but am getting an error on the connect-api container startup
Error: Server: (failed to setupServer), Wrapped: (TLS configuration), load certificate+key: tls: failed to find any PEM data in certificate input
Any guidance on resolving the issue is appreciated.