SSL Autogenerate

Can setting up SSL really be as simple as adding

ssl: {
    autogenerate: {
      email: '[e-mail]',
      domains: 'website.com,www.website.com'
    }
  }

To the meteor object in the mup.js file?

I tried adding this and re-running the mup deploy and mup setup commands. Everything deploys successfully, however my domain is still unsecure.

Are there any more steps I need to take to get this to work? Or can someone help me with troubleshooting?

While running mup setup and deploy I don’t see any messages relating to SSL. I’m also currently on version 1.2.5, I guess I should try this on 1.2.6 but it’s my understanding that this should still work. Here is what I’m seeing.

mup setup

Started TaskList: Setup Docker [boldvue.com] - Setup Docker [boldvue.com] - Setup Docker: SUCCESS

Started TaskList: Setup Meteor [boldvue.com] - Setup Environment [boldvue.com] - Setup Environment: SUCCESS

Started TaskList: Setup Mongo [boldvue.com] - Setup Environment [boldvue.com] - Setup Environment: SUCCESS [boldvue.com] - Copying mongodb.conf [boldvue.com] - Copying mongodb.conf: SUCCESS

Started TaskList: Start Mongo [boldvue.com] - Start Mongo [boldvue.com] - Start Mongo: SUCCESS

And

mup deploy

Your app is using the “force-ssl” package, but ssl is not setup in your mup config. This can cause unexpected redirects. Building App Bundle Locally

Started TaskList: Pushing Meteor App [boldvue.com] - Pushing Meteor App Bundle to The Server [boldvue.com] - Pushing Meteor App Bundle to The Server: SUCCESS

Started TaskList: Configuring App [boldvue.com] - Pushing the Startup Script [boldvue.com] - Pushing the Startup Script: SUCCESS [boldvue.com] - Sending Environment Variables [boldvue.com] - Sending Environment Variables: SUCCESS

Started TaskList: Start Meteor [boldvue.com] - Start Meteor [boldvue.com] - Start Meteor: SUCCESS [boldvue.com] - Verifying Deployment [boldvue.com] - Verifying Deployment: SUCCESS

Thank you, getting the SSL to work and auto-renew is huge. It’s always been a pain to deal with in the past because I only do it once a year and so it’s a struggle to plow through it every time.

[chrissanders]

I was able to get this working, although I’m not sure exactly what fixed it. Things I did were:

1. Change the ROOT_URL from http to https in mup.js
2. Only list one subdomain in the ssl section of mup.js
3. Run mup setup from mup/prod
4. Call ./bin/deploy prod

One of those things or a combination of them got me going.

[kulttuuri]

Nevermind, got this one sorted out! I was trying to sign azure test server address, looked up the docker logs for the nginx meteor server instance and it did not want to grant that server an certificate. Added DNS entry to my own server subdomain address and it worked nicely.

Just heads up that with Azure’s Ubuntu 14.04 server the letsencrypt did not work at all, but with 16.04 it worked out of the box. It also needs few minutes for the certificate to be signed. Good way to check for certificate signing errors is to SSH into the server computer and first run sudo docker ps, get container ID of jrcs/letsencrypt-nginx-proxy-companion:latest and run `sudo docker logs companionContainerID’. That’s where I found the error at.