Cover image for Docker 201: Use NGINX as a Reverse Proxy for NodeJS Server in 2020! πŸ“¦ πŸ™Œ (practical guide)
The Destro Dev Show

Docker 201: Use NGINX as a Reverse Proxy for NodeJS Server in 2020! πŸ“¦ πŸ™Œ (practical guide)

destro_mas profile image Shahjada Talukdar ・3 min read

I will skip "What/Why Docker?" part to make it straight to the point! 🀝

Goal: We are gonna use NGINX as a Reverse Proxy for a NodeJS Server. ⧚

For that, I will use 2 Docker images from Docker Hub - One is for NodeJS and another one is for NGINX 🀞

Let's see this in action!

I have already installed -

  • NodeJS
  • Docker

We will create a simple Node Server. We will use http module from node and make a simple http server. server.js file contains the code of our server-

var http = require('http');

var server = http.createServer(function (request, response) {
  response.writeHead(200, {"Content-Type": "text/plain"});
  response.end("Node & Docker Running...");


console.log("Node HTTP Server started at http://localhost:3333/");

If we run node server.js on our terminal, it will start the server at 3333 port on localhost.
We can open a browser and hit http://localhost:3333/ and we can see server is sending the text Node & Docker Running....
Awesome πŸ‘

Now, we want to create a docker image for our Node Server. To do this, we need to create a file named Dockerfile with the below commands-

FROM mhart/alpine-node
COPY server.js .
CMD node server.js

Here, I have used mhart/alpine-node(Minimal Node.js Docker Image) for having NodeJS environment.

EXPOSE 3333 means - 3333 port is intended to be published.

Now that we have our Dockerfile ready, we will build a Docker image from this file. We can run on the terminal-

docker build -t docknode .

*Here, docknode is the image name. We can use any name.

I will run the docker image now which will make a container for us-

docker run -d -p 3333:3333 --name node-server  docknode

I have used -d which will help to run the container in the background.

After running this command, our NodeJS server should run inside the Docker container named node-server.
Now, if I open any Browser and hit http://localhost:3333, we can see the server is running πŸŽ‰

Ok, awesome! As our NodeJS server inside a Node Docker image is running, we need to add NGINX Reverse Proxy next.

We will use the official NGINX image from DockerHub.
Let's create a Dockerfile for that.

FROM nginx
COPY default.conf /etc/nginx/conf.d/

I am gonna create a file called default.conf for NGINX with the following configurations -

server {
  location / {
    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;
    proxy_pass http://server:3333;

Please note that, here in the configurations, we have http://server:3333. This 3333 is the Port from our NodeJS Docker container. I will come to the server part later in this article.

Let's go to Terminal and run-

docker build -t docknginx .

This will build the docker image for NGINX. After running the command, we will see something like this-

Alt Text

And, to verify that our image is available in our local machine, we can run the below command to see the list-

docker images

Alt Text

Coolio! We can see both of our images are available here πŸ‘

As our goal is to have the NGINX as the Reverse Proxy for our NodeJS Server. When we will run the NGINX image, We need to link the NodeJS Server to NGINX.

To do that, I will run the below command on the Terminal-

docker run -d -p 8080:80 --link node-server:server --name nginx-proxy  docknginx

Here, --link is helping to link our NodeJS Container to this NGINX container. If you double-check, I named the NodeJS Container as node-server. And this :server is used inside our NGINX Configurations. 🀝

After running the command, if we now go to our Browser and hit http://localhost:8080/, we can see our NodeJS App is running on this port now πŸŽ‰

Alt Text

We are actually hitting the NodeJS Server through NGINX as it is working as a Reverse Proxy here.

Awesome πŸ™Œ

I hope, you liked it. And if you haven't used Docker yet, I think, you should Try it in 2020!

See you in my next article.

Till then,

As I am trying to contribute contents on the Web, you can buy me a coffee for my hours spent on all of these ❀️😊🌸
Buy Me A Coffee

Posted on by:

destro_mas profile

Shahjada Talukdar


Senior Software Engineer @eBay. Tech enthusiast, loves JS + few other languages. Keen to learn about Software Engineering/Architecture. πŸ‘‹

The Destro Dev Show

Hub for Cutting edge Software/Web development Podcast and tutorial. made with ❀️ in Berlin!


markdown guide

This is really interesting. Could you eli5 why one would need to use a reverse proxy at all?


One reason is, you have multiple apps/websites hosted on the same server. Say you have a landing/marketing page at myproduct.com and a dashboard for user accounts at app.myproduct.com. They can't both listen port 80 (default http port). You set up a reverse proxy that listens to 80 and forwards traffic to the respective app based on the domain. The apps can listen to ports 3000 and 3001 for example.

Does that make sense?


I think so. Just so im sure i understood your explanation, internally they use 3000 and 3001, and when people hit up myproduct.com and app.myproduct.com, that goes to nginx which then forwards the request to the correct ports?


nice article, just to add more information --link flag is a legacy feature of Docker


Thanks, I will update accordingly πŸ‘


very helpful article .. Thanks for sharing


In the next round, do this with https ;) :D


Will try,
I have a lot of things in my queue πŸ˜€


I think it's will make people confuse between Proxy Vs Reverse Proxy.

If you agree with me please correct these.


Actually, Reverse proxy is the specific term. I will update


nice article, have you any tips about static files? I've been some problems with css and js front end scripts locations


What worked for me was to create a different folder with nginx and use docker compose in order to run and connect everything at the same time. It works fine in development. Here is the repo I have so far:

Since I just started with docker a couple of weeks ago, I can't get it to work on production though. I can make it work with the static files but I can't find a way to start the express API server.

If someone could lend me a hand I'd appreciate it. Here is how my Dockerfile looks so far:

FROM nginx AS static
COPY ./client /app

FROM node:12-alpine AS api
COPY ./server/package.json /app
RUN npm install
COPY ./server /app

FROM nginx
COPY ./nginx/default.conf /etc/nginx/conf.d/default.conf
COPY --from=static /app /usr/share/nginx/html

If I remove the middle section (all the node part) it works fine, but as I said I can't find a way to start the express server.

If you user the code in the repo, running docker-compose up --build is going to work fine, as long as you provide your own mongo database of course.