PEM file not applied

[trevorblades]

When I run surge ssl with my certificate, I get a non-descriptive error saying:

Error - something went wrong. the pem file was not applied

I was able to successfully apply SSL certs to my domains a few months ago, but now it's not working. Any thoughts on what might be going on here?

This was also recently reported on Twitter https://twitter.com/davidweisss/status/755553830129897473

[stuartbreckenridge]

Also getting this error. There doesn't appear to be a way around it as I've tried with certs from several CAs.

@trevorblades did you manage to resolve?

[trevorblades]

@stuartbreckenridge I didn't. I ended up switching over to AWS 😞

[stuartbreckenridge]

@trevorblades Same...I moved to netlify.

[sintaxi]

Sorry you both had issues. This is usually due to the order of your certs in your PEM file.

[stuartbreckenridge]

My PEM file was:

My certificate Rapid SSL Intermediate Private Key

This failed, but so did all (5) other combinations possible.

On 24 Aug 2016, at 6:31 am, Brock Whitten notifications@github.com<mailto:notifications@github.com> wrote:

Sorry you both had issues. This is usually due to the order of your certs in your PEM file.

You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/sintaxi/surge/issues/219#issuecomment-241901038, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGuF_JP_Y1U9m0QVy1oRNmN_H50WsCehks5qi3SwgaJpZM4JRZwe.

[sintaxi]

@stuartbreckenridge what you did seems right. There must be something else causing the error. We will dig further into this. Thanks for following up and reporting the issue.

[famulus]

I'm getting the same issue

[calvinbrewer]

+1 Same error here.

PEM file:

Certificate Private key

[jmspswny]

Same error here. Have the problem with a number of domains, and all permutations of .key and .crt files within the .pem

[tigarcia]

I had a similar problem while using let's encrypt. I found this digital ocean let's encrypt tutorial helpful. Surge uses digital ocean, so any info on how to get your cert on digital ocean will probably apply to surge.

[matteodem]

what's the status on this issue?

[srobertson421]

I also had this issue, am using SSLMate cert. My problem was that I had the order wrong when I concatenated. The order should be:

cat mydomain.crt mydomain.chain.crt mydomain.key > surge.pem

This worked for me, basically the ".chain" crt was an intermediary cert so start with your main domain cert, then do each intermediary cert, finally include your key file.

[tylerdave]

I'm having this same issue today trying to upload a new certificate to an account that already had one (and that has now expired.) It's using a LetsEncrypt cert. I've tried:

cat fullchain.pem privkey.pem > surge.pem cat cert.pem privkey.pem > surge.pem cat cert.pem chain.pem privkey.pem > surge.pem

In every case running the surge ssl command w/ the pem file results in:

Error - the pem file was not applied

I'm pretty sure I followed the same process for uploading the original cert so I don't know why it's failing now. It'd be nice if the error output gave some indication of what the error is and not just that there's an error.

[sintaxi]

@tylerdave if you're able to hop into slack I can help you.

[nickFalcone]

I am having the same issue. I've tried running surge ssl and going through the prompts - resulting in Error - the pem file was not applied.

I also tried surge --pem surge.pem --domain https://mydomain.com - resulting in Success! Project is published and running at mydomain.com

I followed the surge ssl guide and have also tried this person's guide.

@sintaxi - any advice?

[sintaxi]

@nickFalcone can you email support@surge.sh with more details such as your domain and Certificate Authority if you have one?

[Sewdn]

@sintaxi I'm having the same issue as @nickFalcone and contacted your support 4days ago as you suggested. I still didn't receive any feedback and my issue is not resolved.

@nickFalcone Is you issue resolved now? Thanks!

[guyjacks]

We're having this issue with Let's Encrypt certs.

[marcelocpinheiro]

Here's a good guide https://community.letsencrypt.org/t/adding-certbot-ssl-certification-to-custom-domain-on-surge/88241

[arturojain]

Anyone found a fix for this?