How to Build Your Own Communication Platform with Rocket.chat?

Step 4: -Setting Up a Reverse Proxy with Nginx with SSL

To start, install Nginx.<>

sudo apt-get install -y nginx

Move your certificate’s private key file to the nginx folder /etc/nginx/certificate.key.<>

sudo cp /path/to/your/key /etc/nginx/certificate.key

For example,

if you created a now Let’s Encrypt certificate, you would use<>

sudo cp /etc/letsencrypt/live/your_domain_name/privkey.pem /etc/nginx/certificate.key.

sudo chmod 400 /etc/nginx/certificate.key

sudo cp /path/to/your/cert /etc/nginx/certificate.crt

the command is like <>

sudo cp /etc/letsencrypt/live/your_domain_name/cert.pem /etc/nginx/certificate.crt
We are going to create an entirely new configuration for Rocket.Chat, so you can remove the default/existing to make it easier.<>

sudo rm /etc/nginx/sites-enabled/default

If you need that file back in the future, it is still available at/etc/nginx/sites-available/default.

now, Create a new/etc/nginx/sites-enabled/defaultwith nano or your favourite text editor <>

sudo nano /etc/nginx/sites-enabled/default

First, we’ll add an upstream block:

Now let’s create a server block. The first part tells Nginx which port to listen for connections on, in this case :443. It also allows it to know what our hostname is example.com.

Don’t forget to replace example.com with your domain name.

Under that part, we tell Nginx where they can find the Rocket.Chat’s access logs, and we point it to the SSL certificate and key we placed in/etc/nginx/certificate.key and /etc/nginx/certificate.crt, respectively.

And now, let's finish the configuration off with a location block:

location / {
    proxy_pass http://example.com:3000/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forward-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forward-Proto http;
    proxy_set_header X-Nginx-Proxy true;
    proxy_redirect off;
    }
}