Domain managment: certificate is not a valid pem certificate

[Ulrik7000]

My site is drywallmagana.com
i get this error message when writing the codes for my certificate “certificate is not a valid pem certificate” I tried all possible combinations opening the .crt files with text editor but i still get this message, are there ways to identify which of the files represent the PEM cert, private key, and intermediate certs?
I got my cert from namecheap

[elden]

Hi @Ulrik7000,

Did you happen to stumble across this community post yet?

[Support Guide] Tips for bringing your own custom SSL certificates to Netlify

Hi there! While it’s not a very common occurrence, you may decide to bring your own custom TLS/SSL certificate to provide HTTPS for your Netlify site. Here are some tips that might be helpful in that instance. Also, our HTTPS (SSL) docs include guidelines on what you’ll need to enter in the Netlify app and where to go to enter it. If you’re stuck with questions about how to format those items, or you need to work with your external certificate provider to troubleshoot the custom cert, here are …

That is the best information we have on using customer certificates. Take a look and see if that helps!

Thanks,

Elden

[Ulrik7000]

I’ve followed the instructions on this post, similar to others, but i still cant make my certificates match what netlify needs, is there common mistakes people make when trying to install custom certs?

[hrishikesh]

This is how your certificate should look:

Certificate is not a valid PEM certificate

Hard to say without being able to see your certificate. I know that feature works since I just added a test certificate to a test site successfully, but also not sure why you’d use a godaddy certificate instead of ours? Below you’ll see demonstrated the formats your certificates should have. Note that each should line-wrap at exactly the 64th character for the body of the keys or certificates and have no escape characters before the line breaks: hc3nnKTe9/oyXiU1vnWJj4AwBHcBBn3GtfooChNteiuoRV…

[Ulrik7000]

thats how mines look like, I got 3 files, pem file, pkcs #7 and a bundle

[audrey]

@Ulrik7000 something to check for is did you decrypt the private key?

[Ulrik7000]

Hi Audrey the way I’m obtaining the code is by pasting the document directly to a txt file. Can you tell me which ways can I use to decrypt the private key?

[elden]

Continuing the discussion from Domain managment: certificate is not a valid pem certificate:

Hi @Ulrik7000

Could you send us the first few characters of each section of your certificate as shown in the article Hrishikesh sent you previously: Certificate is not a valid PEM certificate - #2 by fool. I mean like thisL:

CA Chain:

-----BEGIN CERTIFICATE-----
MIIFADC[...]
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
[...]

Cert PEM file:

-----BEGIN CERTIFICATE-----
MIIF[...]
-----END CERTIFICATE-----

Private Key:

-----BEGIN PRIVATE KEY-----
MC[...]
-----END PRIVATE KEY-----

Also, could you use the developer tools in your browser to capture the x-nf-request-id-header when you see the error message after submitting your certificate? Here’s how to get it:

[Support Guide] Netlify Support asked for the 'x-nf-request-id' header? What is it and how do I find it?

Last reviewed by Netlify Support staff August 2023 What is the x-nf-request-id header? Web servers and web browsers communicate using a protocol called HTTP - which stands for “HyperText Transfer Protocol”. Both web browsers and web servers use a feature called headers as part of this protocol. The headers that web browsers send are called “request headers” because the browser in making an “HTTP request”. The web servers headers are called “response headers” because web servers send an “HTTP …

Thanks,

Elden

[Ulrik7000]

Yes thank you elden, this are the first few characters and the x-nf-request-id-header:
CA Chain:

-----BEGIN CERTIFICATE-----
MIIGEzC[...]
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIFgTC[...]
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIEMjC[...]
-----END CERTIFICATE-----

Cert PEM file:

-----BEGIN CERTIFICATE-----
MIIGQDC[...]
-----END CERTIFICATE-----

Private Key:

-----BEGIN PRIVATE KEY-----
MIIWQQY[...]
-----END PRIVATE KEY-----

x-nf-request-id:

01G8YFE8DKM748WF5NP2FPS548

[Ulrik7000]

Namecheap reps facilitated this link for me (CSR Generator) which, while being logged in, enabled me to get the 3 codes netlify needed me to input to install my SSL certificate successfully

[hillary]

That is great! Thanks for coming back and letting us know.

[Ulrik7000]

Now that I fixed this a couple days ago its giving me some troubles when trying to access my website. On my netlify dashboard it says " Your site has HTTPS enabled" but when I try to open my website, it still sends me a privacy error notification

[fool]

I see at least two problems with your SSL certificate.

First, you got one only for the bare domain. why not www as well? It is ok but if we ever serve www it will not work well.

Second, something is still wrong with the certificate. namecheap should be able to help you address the problems: SSL Server Test: drywallmagana.com (Powered by Qualys SSL Labs)