My problem: I want to build a website with WordPress as the content management system. However, I don’t want to make use of its frontend template, instead, I will expose REST API from WordPress and have a dedicated Frontend WebApp using Nextjs.Below is the diagram:<img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/1_9_JDI_Qk_G6_UO_Zd_Wg3_VB_7v_Ovg_f2d0125948.webp" alt="1_9JDIQkG6UOZdWg3VB7vOvg.webp" srcset="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/thumbnail_1_9_JDI_Qk_G6_UO_Zd_Wg3_VB_7v_Ovg_f2d0125948.webp 128w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/small_1_9_JDI_Qk_G6_UO_Zd_Wg3_VB_7v_Ovg_f2d0125948.webp 411w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/medium_1_9_JDI_Qk_G6_UO_Zd_Wg3_VB_7v_Ovg_f2d0125948.webp 616w," sizes="100vw"><img class="image_resized" style="width:680px;" src="https://miro.medium.com/v2/resize:fit:700/1*9JDIQkG6UOZdWg3VB7vOvg.png" alt="" loading="eager">Prerequisites:<ul><li>Basic knowledge of SSH into an EC2 server (or any other VPS) and Ubuntu commands, or ability to read documentation for ubuntu commands.</li><li>I have a domain name mydomain.com</li><li>I purchased a wildcard SSL certificate for my domain: *.mydomain.com</li><li>I already setup SSL for my domain: *.mydomain.com</li><li>I created manually an AWS EC2 instance.</li><li>I have a Wordpress backend service to serve REST API at port 8000</li><li>I also have a Wordpress CMS app running at port 8000</li><li>I have a frontend app running at port 3001</li></ul>*Please note that you’re freely to choose the port number.<h2 style="margin-left:0px;">I choose to use Nginx as a reverse proxy server to configure the domain.</h2>&nbsp;Now, let’s jump into the main objective of this blog post.<h2 style="margin-left:0px;">Step 0:</h2><ul><li>Navigate to `/etc/nginx/sites-enabled/` and edit <code>default</code> file using <code>sudo vim default</code></li><li>Better to backup it first by the command <code>mv default defaultbk</code></li></ul><h2 style="margin-left:0px;">Step 1: Configure Nextjs Frontend webapp at port 3001</h2><img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/1_36x_C8v_G_Sdw_ENL_11l_UHQ_0zg_c2de1ce2a1.webp" alt="1_36xC8vGSdwENL11lUHQ0zg.webp" srcset="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/thumbnail_1_36x_C8v_G_Sdw_ENL_11l_UHQ_0zg_c2de1ce2a1.webp 245w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/small_1_36x_C8v_G_Sdw_ENL_11l_UHQ_0zg_c2de1ce2a1.webp 500w," sizes="100vw">we are at this part<pre><code class="language-plaintext">#Nextjs FE app: remove www to avoid canonnical issue
server {
 listen 80;
 listen 443 ssl;

 # Certificate
 ssl_certificate /etc/nginx/ssl/STAR_mydomain.crt;

 # Private Key
 ssl_certificate_key /etc/nginx/ssl/STAR_mydomain.key;

 server_name http://mydomain.com www.mydomain.com;
 return 301 https://mydomain.com$request_uri;
}

#Nextjs FE app: force ssl for mydomain.com (main domain)
server {
 listen 80;
 server_name http://mydomain.com mydomain.com www.mydomain.com;
 return 301 https://mydomain.com$request_uri;
}

#Nextjs FE app: point main domain (Frontend) to port 3001 of Nextjs
server {
 listen 443 ssl;
 listen [::]:443 ssl;
 
 server_name mydomain.com;
 # Certificate
 ssl_certificate /etc/nginx/ssl/STAR_mydomain.crt;

 # Private Key
 ssl_certificate_key /etc/nginx/ssl/STAR_mydomain.key;
 location / {
 proxy_pass http://localhost:3001;
 proxy_set_header Host $host;
 proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_set_header X-Forwarded-Proto $scheme;
 }
}</code></pre><h2 style="margin-left:0px;">Step 2: Configure the REST API:</h2><img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/1_Ip_N_Xpt1of_FB_Kpdu9w6_HM_7w_8d833916e8.webp" alt="1_IpNXpt1ofFBKpdu9w6HM7w.webp" srcset="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/thumbnail_1_Ip_N_Xpt1of_FB_Kpdu9w6_HM_7w_8d833916e8.webp 245w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/small_1_Ip_N_Xpt1of_FB_Kpdu9w6_HM_7w_8d833916e8.webp 500w," sizes="100vw">we are at this part<pre><code class="language-plaintext">#REST API: force ssl for api.mydomain.com (wordpress backend)
server {
 listen 80;
 server_name api.mydomain.com;
 return 301 https://api.mydomain.com$request_uri;
}

#REST API: point api.mydomain.com to port 8000
server {
 listen 443 ssl;
 listen [::]:443 ssl;

 server_name api.mydomain.com http://api.mydomain.com;
 # Certificate
 ssl_certificate /etc/nginx/ssl/STAR_mydomain.crt;

 # Private Key
 ssl_certificate_key /etc/nginx/ssl/STAR_mydomain.key;
 location / {
 proxy_pass http://localhost:8000;
 }
}</code></pre><h2 style="margin-left:0px;">Step 3: Configure the CMS</h2><img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/1_7_Atk_F4_RGNQ_1_16_At0_H_No_ZA_7baba811f1.webp" alt="1_7AtkF4RGNQ1_16At0HNoZA.webp" srcset="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/thumbnail_1_7_Atk_F4_RGNQ_1_16_At0_H_No_ZA_7baba811f1.webp 241w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/small_1_7_Atk_F4_RGNQ_1_16_At0_H_No_ZA_7baba811f1.webp 500w," sizes="100vw">we are at this part<pre><code class="language-plaintext">#CMS: force ssl for cms.mydomain.com (wordpress cms)
server {
 listen 80;
 server_name cms.mydomain.com http://cms.mydomain.com;
 return 301 https://cms.mydomain.com$request_uri;
}

#CMS: point cms.mydomain.com to port 8000
server {
 listen 443 ssl;
 listen [::]:443 ssl;

 server_name cms.mydomain.com;
 # Certificate
 ssl_certificate /etc/nginx/ssl/STAR_mydomain.crt;

 # Private Key
 ssl_certificate_key /etc/nginx/ssl/STAR_mydomain.key;
 location / {
 proxy_pass http://localhost:8000;
 proxy_set_header Host $http_host;
 proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_set_header X-Forwarded-Proto $scheme;
 }
}</code></pre><h2 style="margin-left:0px;">Full configuration</h2><pre><code class="language-plaintext">
#Nextjs FE app: remove www to avoid canonnical issue
server {
 listen 80;
 listen 443 ssl;

 # Certificate
 ssl_certificate /etc/nginx/ssl/STAR_mydomain.crt;

 # Private Key
 ssl_certificate_key /etc/nginx/ssl/STAR_mydomain.key;

 server_name http://mydomain.com www.mydomain.com;
 return 301 https://mydomain.com$request_uri;
}

#Nextjs FE app: force ssl for mydomain.com (main domain)
server {
 listen 80;
 server_name http://mydomain.com mydomain.com www.mydomain.com;
 return 301 https://mydomain.com$request_uri;
}

#Nextjs FE app: point main domain (Frontend) to port 3001 of Nextjs
server {
 listen 443 ssl;
 listen [::]:443 ssl;
 
 server_name mydomain.com;
 # Certificate
 ssl_certificate /etc/nginx/ssl/STAR_mydomain.crt;

 # Private Key
 ssl_certificate_key /etc/nginx/ssl/STAR_mydomain.key;
 location / {
 proxy_pass http://localhost:3001;
 proxy_set_header Host $host;
 proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_set_header X-Forwarded-Proto $scheme;
 }
}

#REST API: force ssl for api.mydomain.com (wordpress backend)
server {
 listen 80;
 server_name api.mydomain.com;
 return 301 https://api.mydomain.com$request_uri;
}

#REST API: point api.mydomain.com to port 8000
server {
 listen 443 ssl;
 listen [::]:443 ssl;

 server_name api.mydomain.com http://api.mydomain.com;
 # Certificate
 ssl_certificate /etc/nginx/ssl/STAR_mydomain.crt;

 # Private Key
 ssl_certificate_key /etc/nginx/ssl/STAR_mydomain.key;
 location / {
 proxy_pass http://localhost:8000;
 }
}

#CMS: force ssl for cms.mydomain.com (wordpress cms)
server {
 listen 80;
 server_name cms.mydomain.com http://cms.mydomain.com;
 return 301 https://cms.mydomain.com$request_uri;
}

#CMS: point cms.mydomain.com to port 8000
server {
 listen 443 ssl;
 listen [::]:443 ssl;

 server_name cms.mydomain.com;
 # Certificate
 ssl_certificate /etc/nginx/ssl/STAR_mydomain.crt;

 # Private Key
 ssl_certificate_key /etc/nginx/ssl/STAR_mydomain.key;
 location / {
 proxy_pass http://localhost:8000;
 proxy_set_header Host $http_host;
 proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_set_header X-Forwarded-Proto $scheme;
 }
}</code></pre><h2 style="margin-left:0px;">Last step:</h2><ul><li>Reload and restart Nginx with <code>sudo systemctl reload nginx</code> and <code>sudo systemctl restart nginx</code></li></ul>I hope this helps not only with the configuration but the overall understanding of your own use cases.

My problem: I want to build a website with WordPress as the content management system. However, I don’t want to make use of its frontend template, instead, I will expose REST API from WordPress and have a dedicated Frontend WebApp using Nextjs.

Configure NGINX to host both Backend and Frontend servers in one AWS EC2 instance

1. What is Docker ?:Docker is a software platform that allows you to build, test, and deploy applications quickly. Docker packages software into standardized units called containers that have everything the software needs to run including libraries, system tools, code, and runtime. Using Docker, you can quickly deploy and scale applications into any environment and know your code will run.2. How Docker work ?:Docker works by providing a standard way to run your code. Docker is an operating system for containers. Similar to how a virtual machine virtualizes (removes the need to directly manage) server hardware, containers virtualize the operating system of a server. Docker is installed on each server and provides simple commands you can use to build, start, or stop containers.<img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/Docker_Engine_Structure_d54eef4c33.png" alt="Docker Engine Structure" srcset="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/thumbnail_Docker_Engine_Structure_d54eef4c33.png 245w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/small_Docker_Engine_Structure_d54eef4c33.png 500w," sizes="100vw">3. Docker image:A Docker image is a read-only template that contains a set of instructions for creating a container that can run on the Docker platform. It provides a convenient way to package up applications and preconfigured server environments, which you can use for your own private use or share publicly with other Docker users.4. Docker container:A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another. A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries, and settings.<img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/Docker_Container_Structure_2b2c666b01.png" alt="Docker Container Structure" srcset="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/thumbnail_Docker_Container_Structure_2b2c666b01.png 180w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/small_Docker_Container_Structure_2b2c666b01.png 500w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/medium_Docker_Container_Structure_2b2c666b01.png 750w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/large_Docker_Container_Structure_2b2c666b01.png 1000w," sizes="100vw">5. Docker volume:Volumes are the preferred mechanism for persisting data generated by and used by Docker containers. While bind mounts are dependent on the directory structure and OS of the host machine, volumes are completely managed by Docker. Volumes have several advantages over bind mounts:<ul><li>Volumes are easier to back up or migrate than bind mounts.</li><li>You can manage volumes using Docker CLI commands or the Docker API.</li><li>Volumes work on both Linux and Windows containers.</li><li>Volumes can be more safely shared among multiple containers.</li><li>Volume drivers let you store volumes on remote hosts or cloud providers, to encrypt the contents of volumes, or add other functionality.</li><li>New volumes can have their content pre-populated by a container.</li><li>Volumes on Docker Desktop have much higher performance than bind mounts from Mac and Windows hosts</li></ul>6. Docker network:One of the reasons Docker containers and services are so powerful is that you can connect them together, or connect them to non-Docker workloads. Docker containers and services do not even need to be aware that they are deployed on Docker, or whether their peers are also Docker workloads or not. Whether your Docker hosts run Linux, Windows, or a mix of the two, you can use Docker to manage them in a platform-agnostic way.<img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/Docker_network_3e3e8830b8.png" alt="Docker network" srcset="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/thumbnail_Docker_network_3e3e8830b8.png 227w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/small_Docker_network_3e3e8830b8.png 500w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/medium_Docker_network_3e3e8830b8.png 750w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/large_Docker_network_3e3e8830b8.png 1000w," sizes="100vw">7. Docker Hub:Share and Collaborate with Docker Hub. Docker Hub is the world’s largest repository of container images with an array of content sources including container community developers, open-source projects, and independent software vendors (ISV) building and distributing their code in containers. Users get access to free public repositories for storing and sharing images or can choose a subscription plan for private repos.<img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/Docker_Hub_5caefb391b.png" alt="Docker Hub" srcset="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/thumbnail_Docker_Hub_5caefb391b.png 245w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/small_Docker_Hub_5caefb391b.png 500w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/medium_Docker_Hub_5caefb391b.png 750w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/large_Docker_Hub_5caefb391b.png 1000w," sizes="100vw">8. How to use Docker with docker-compose and Docker Hub:<ol><li>What about docker-compose:</li></ol>Docker Compose is a tool that was developed to help define and share multi-container applications. With Compose, we can create a YAML file to define the services and with a single command, can spin everything up or tear it all down.The big advantage of using Compose is you can define your application stack in a file, keep it at the root of your project repo (it’s now version controlled), and easily enable someone else to contribute to your project. Someone would only need to clone your repo and start the compose app. In fact, you might see quite a few projects on GitHub/GitLab doing exactly this now.<ol><li>How to install PostgreSQL with Docker Hub and docker compose:</li></ol><ul><li>Download Office Postgres Image from Docker Hub with the command:<ul><li>docker pull postgres</li></ul></li><li>Attention: We can use docker run with a lot of parameters to run this database, but this way is very confusing, so I recommend using docker-compose instead.</li><li>Create docker-compose.yml:</li></ul><pre><code class="language-plaintext"># Use postgres/example user/password credentials
version: '3.1'

services:

 &nbsp;db:
 &nbsp;&nbsp;&nbsp;image: postgres
 &nbsp;&nbsp;&nbsp;restart: always
 &nbsp;&nbsp;&nbsp;environment:
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;POSTGRES_PASSWORD: postgres
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;POSTGRES_USER: postgres
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;POSTGRES_DB: postgres
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ports:
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- 5436:5432
 &nbsp;adminer:
 &nbsp;&nbsp;&nbsp;image: adminer
 &nbsp;&nbsp;&nbsp;restart: always
 &nbsp;&nbsp;&nbsp;ports:
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- 8080:8080</code></pre><ul><li>Open terminal, change directory to folder that contain this docker-compose.yml file, then type below command: docker-compose up -d</li><li>Open localhost:8080 to open adminer with password=postgres and fill the value for other input like this image:<img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/Adminer_Login_2e5c1ebcf2.png" alt="Adminer Login" srcset="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/thumbnail_Adminer_Login_2e5c1ebcf2.png 245w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/small_Adminer_Login_2e5c1ebcf2.png 500w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/medium_Adminer_Login_2e5c1ebcf2.png 750w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/large_Adminer_Login_2e5c1ebcf2.png 1000w," sizes="100vw"><img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/Docker_Adminer_Logined_b00fa87aaf.png" alt="Docker Adminer Logined" srcset="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/thumbnail_Docker_Adminer_Logined_b00fa87aaf.png 245w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/small_Docker_Adminer_Logined_b00fa87aaf.png 500w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/medium_Docker_Adminer_Logined_b00fa87aaf.png 750w,https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/large_Docker_Adminer_Logined_b00fa87aaf.png 1000w," sizes="100vw"></li></ul>&nbsp;9. Why Use Docker:Using Docker lets you ship code faster, standardize application operations, seamlessly move code, and save money by improving resource utilization. With Docker, you get a single object that can reliably run anywhere. Docker's simple and straightforward syntax gives you full control. Wide adoption means there's a robust ecosystem of tools and off-the-shelf applications that are ready to use with Docker. &nbsp;

Docker is a software platform that allows you to build, test, and deploy applications quickly. Docker packages software into standardized units called containers that have everything the software needs to run including libraries, system tools, code, and runtime. Using Docker, you can quickly deploy and scale applications into any environment and know your code will run.

Explore And Learn Basic Knowledge about Docker

Buy a domain name from Namecheap, You will learn how to set up SSL, mutli domain name like yourwebsite.com, admin.yourwebsite.com and api.yourwebsite.com. And with nginx service we will handle that in one Ubuntu server. Let me show you my tutorial.Buy SSL on any provider, here we're using Namecheap. <img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/image_a282fa11c9.png">Let's just use the cheapest one, you can figure out what are the different between each option later.Once purchased, we have the new SSL available to use:<figure class="image"><img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/image_582546996b.png"></figure>Click on “Activate”:<figure class="image"><img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/image_1ee0ce7a55.png"></figure>Now, let's connect to your EC2 and generate new CSR for your domain:To generate CSR in ubuntu, we must SSH connect to EC2 and use following command:<pre><code class="language-plaintext">openssl req -new -newkey rsa:2048 -nodes -keyout yourwebsite.key -out yourwebsite.csr</code></pre>then fill information for the following section below:<ol><li>Country Name (2 letter code) [US]</li><li>State or Province Name (full name) [BC]</li><li>Locality Name (e.g., city) [Vancouver]</li><li>Organization Name (e.g., company) [My Company Ltd]</li><li>Organizational Unit Name (e.g., section)</li><li>Common Name (e.g., your name or your server’s hostname)</li><li>Email Address</li></ol>If your website have front end and backend on the same server, I suggest you to use wildcard as common name. For example, I want domain yourwebsite.com point to front end, and domain api.yourwebsite.com point to backend. In order to do that, I will fill common name like this “*.yourwebsite.com”.After filling full of information above, you will see "extra" section (Password, Optional name, ..), in this step, please press enter and don't type any thing to skip this section.&nbsp;After that copy content from yourwebsite.csr and fill to SSL INFO form.And keep in eye on yourwebsite.key, you will use it later.<figure class="image"><img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/image_90fbdcfcea.png"></figure>Now add CNAME to activate the SSL<figure class="image"><img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/image_e5ac8662c2.png"></figure>Get record: <img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/image_984f406dc7.png">Add CNAME to the domain config:<figure class="image"><img src="https://abc-cms-production.s3.ap-southeast-1.amazonaws.com/image_ed6cfad9eb.png"></figure>Next step, is depend for your Web service and server. We will use nginx to handle this.First let install nginx by command:<pre><code class="language-plaintext">sudo apt update
sudo apt install nginx</code></pre>Then we remove default config:<pre><code class="language-plaintext">sudo rm -rf /etc/nginx/sites-enabled/default</code></pre>Then create your own config file for web server:<pre><code class="language-plaintext">sudo vim /etc/nginx/sites-enabled/yourwebsite</code></pre>The content of the config file will include two sections: Listen SSL through port 443 and Listen to web server from port 80 or another port. A tip for port 80 that, if your server host a lot of website, I recommend you not to use port 80 any more.<pre><code class="language-plaintext">#force ssl for www.yourwebsite.com
server {
 server_name yourwebsite www.yourwebsite.com;
 return 301 https://yourwebsite.com$request_uri;
}

#point yourwebsite.com to port 3000 (Especially for Next.JS)
server {
 listen 443 ssl;
 listen [::]:443 ssl;

 server_name yourwebsite www.yourwebsite.com;
 
 # Certificate
 ssl_certificate /etc/nginx/ssl/yourwebsite.crt;
 
 # Private Key
 ssl_certificate_key /etc/nginx/ssl/yourwebsite.key;
 location / {
 proxy_pass http://localhost:3000;
 proxy_set_header Host $http_host;
 proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_set_header X-Forwarded-Proto $scheme;
 }
}

#force ssl for api.yourwebsite.com
server {
 server_name api.yourwebsite www.api.yourwebsite.com;
 return 301 https://api.yourwebsite.com$request_uri;
}

#point api.yourwebsite.com to port 3001
server {
 listen 443 ssl;
 listen [::]:443 ssl;

 server_name api.yourwebsite www.api.yourwebsite.com;
 
 # Certificate
 ssl_certificate /etc/nginx/ssl/yourwebsite.crt;
 
 # Private Key
 ssl_certificate_key /etc/nginx/ssl/yourwebsite.key;
 location / {
 proxy_pass http://localhost:3001;
 proxy_set_header Host $http_host;
 proxy_set_header X-Real-IP $remote_addr;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_set_header X-Forwarded-Proto $scheme;
 }
}
</code></pre>Oh what about Certificate and Private Key:You will receive certificate key from email, after you fill your csr key to SSL Info form, copy that content of certificate key and create this file to paste this content.<pre><code class="language-plaintext">sudo vim /etc/nginx/ssl/yourwebsite.crt</code></pre>And private key you get from step (Generate CSR), copy that file to path&nbsp;<pre><code class="language-plaintext">/etc/nginx/ssl/yourwebsite.key</code></pre>After that, run this command to reload your nginx config.<pre><code class="language-plaintext">sudo systemctl reload nginx.service</code></pre>

Buy a domain name from Namecheap, You will learn how to set up SSL, mutli domain name like yourwebsite.com, admin.yourwebsite.com and api.yourwebsite.com. And with nginx service we will handle that in one Ubuntu server.

Devops

Contact Us