SSL key and certificate created as folders when ssl config is incorrect

Hi, I only found a corresponding issue on arunoda/meteor-up #651, so I open it here too as it happened to me using this version too.

I am using Meteor 1.4, and I had a mistake in my mup.js, as I set up

ssl : {
certificate : "./foo.crt",
key : "./bar.crt",
...

instead of

ssl : {
crt: "./foo.crt",
...

This mistake led to the creation of /opt/myWonderfulApp/config/bundle.crt/ and /opt/myWonderfulApp/config/private.key/ folders instead of files on the server.

After fixing my mup.js, mup setup failed with the Copying SSL Certificate Bundle: FAILED message, as it could not create the bundle.crt and private.key files on server.

Deleting /opt/myWonderfullApp fixed it.

That’s clearly tricky to debug, as there are no message when the ssl config is wrong and mup (or docker ?) creates folders instead of files in this case.

[vedovato]

Yo tip to delete the app from /opt/ saved me from wasting more than 2 already wasted weeks! Tks

[zodern]

In the next release it will delete the old certificate and key before uploading. The validator currently warns about many problems with the SSL config.