---
title: "Discussion on \"Configuring NGINX as a Web Server, a Load Balancer and a Reverse Proxy\" | Hashnode"
description: "Discussion on \"Configuring NGINX as a Web Server, a Load Balancer and a Reverse Proxy\". In this simple hands-on, we’ll be configuring Nginx as a Web Server serving static web contents, as a Load Balancer distributing requests to three backend node.js applications and as a Reverse Proxy proxying requests from one port to another.\nNginx :..."
url: "https://hashnode.com/posts/configuring-nginx-as-a-web-server-and-a-load-balancer/66fc09a08fc33cd7acb5ad7d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Configuring NGINX as a Web Server, a Load Balancer and a Reverse Proxy](https://jubriledun.hashnode.dev/configuring-nginx-as-a-web-server-and-a-load-balancer?utm_source=hashnode&utm_medium=feed)

In this simple hands-on, we’ll be configuring Nginx as a Web Server serving static web contents, as a Load Balancer distributing requests to three backend node.js applications and as a Reverse Proxy proxying requests from one port to another. Nginx :...

Oct 1, 2024 · 3 min read · jubriledun.hashnode.dev  
Read the article

-   [#webserver](https://hashnode.com/tag/webserver)
-   [#nginx](https://hashnode.com/tag/nginx)
-   [#loadbalancingnginx](https://hashnode.com/tag/loadbalancingnginx)
-   [#reverse-proxy](https://hashnode.com/tag/reverse-proxy)

## Written by

[Jubril Edun](https://hashnode.com/@jubriledun)

@jubriledun · Lagos, Nigeria

  
[View profile](https://hashnode.com/@jubriledun)

Cloud Engineering Student

Hi there, My name is Jubril Edun, a tech enthusiast who is on a learning journey into the world of Cloud Engineering, Cybersecurity and beyond. Join me as I document my learning journey.

## Responses 2

Markdown supported · ⌘↵ to post

[Node Edge Ops](https://hashnode.com/@nodeedgeops)

[Oct 31](https://hashnode.com/posts/configuring-nginx-as-a-web-server-and-a-load-balancer/66fc09a08fc33cd7acb5ad7d/comment/6ae537969e7c87c38ce4182b)

When nginx is both static server and load balancer I keep upstream keepalive on and size worker\_connections for client plus upstream sockets, not just peak RPS. least\_conn beats round-robin when backends have uneven request cost. After changes I check error\_log for connect() failed vs upstream timed out so I know whether to fix a dead peer or raise proxy\_read\_timeout.