SSL No 2

Hom

Let’s Encrypt SSL, Nginx, MUP → Deployment (Meteor)

Nginx used for SSL setup

Let’s Encrypt free SSL certificate:

Use the instructions on this page to use OpenSSL to create your certificate signing request (CSR) and then to install your SSL certificate on your Nginx server. Restart Note: After you've installed your SSL/TLS certificate and configured the server to use it, you must restart your Nginx instance.

Let’s start by generating

Add a A Record in your domain’s DNS Settings

Setting up Let’s Encrypt

• ssh into your server console and run following commands

$ wget https://dl.eff.org/certbot-auto
$ chmod a+x certbot-auto
$ ./certbot-auto certonly -d yourdomain.com --standalone

After successful execution of the last command you can see your Certificate & Key generated in /etc/letsencrypt/yourdomain.com

Setting up Nginx

• Let’s install nginx which will be our proxy server

$ sudo apt-get install nginx

• Use nano to create / edit your domain’s nginx settings:

$ sudo nano /etc/nginx/sites-enabled/yourdomain.com.conf

Below is the code that tells the server what to do. We listen to port 80 for domain.com and 301 redirect that to https://yourdomain.com, append the requested uri and listen on port 443 for our ssl set up.

Now check your nginx settings. 

Run:  $ sudo nginx -t



That should return


nginx: the configuration file /etc/nginx/nginx.conf syntax is ok


nginx: configuration file /etc/nginx/nginx.conf test is successful



If it returns an error, nginx will tell you which file and line number contains the error. Simply sudo nano to edit the file at the path name.



Now you have to restart nginx and you’ll be up and running.

$ sudo service nginx restart

Setting up MUP

Installing mup

$ npm install -g mup

You can create a directory .deploy in your project and initialize MUP

$ mkdir .deploy
$ mup init

After mup init following file will be generated and then you can edit it according to your needs.

MUP Config

yourdomain.com.conf file

server {
   ...
   location {
      ...
      proxy_pass http://localhost:3000;
      ...
   }
   ...
}

mup.js

meteor {
   ...
   env {
      ...
      PORT: 3000,
      ROOT_URL: http://localhost
      ...
   }
   ...
}

Keep in mind we will have to use the same ROOT_URL & PORT in MUP env and yourdomain.com.conf file

$ mup setup

$ mup deploy

Your app is deployed and you can access it on https://yourdomain.com.

References:

• https://johngibby.com/blog/How_to_use_LetsEncrypt_with_Multiple_Domains_on_Nginx_and_Ubuntu
• https://johngibby.com/blog/How_to_deploy_your_meteor.js_app_on_Digital_Ocean
• https://certbot.eff.org/#ubuntutrusty-nginx

• Meteor
• Lets Encrypt
• Nginx
• Ssl
• Mup

Like what you read? Give Ibrahim Zahoor a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.

Ibrahim Zahoor

Technology Entreprenuer

Qbatch

We are a Web Development company based in Lahore, Pakistan

Top on Medium

Sex, Beer, and Coding: Inside Facebook’s Wild Early Days in Palo Alto

WIRED

Top on Medium

The Cost Of JavaScript In 2018

Addy Osmani

Top on Medium

I Love My Mac, but Apple Just Isn't Fun Anymore

Noah Halford

Responses

Applause from Ibrahim Zahoor (author)

Hassan Akram

Sep 19, 2016

Nice article.

Conversation with Ibrahim Zahoor.

Pasha Brunko

Jan 16, 2017

Ibrahim Zahoor Thanks for the great article! I have an issue, though.. How can we handle getting right Meteor.absoluteUrl() in this case? Except for setting additional env variable.

1 response

Ibrahim Zahoor

Jan 16, 2017

You can follow another method too which is SSL config using meteor-up

1 response

Never miss a story from Qbatch, when you sign up for Medium. Learn more