https://github.com/atkaridarshan04/nginx-reverseproxy-demo

Setup and configure Nginx as Reverse Proxy.
https://github.com/atkaridarshan04/nginx-reverseproxy-demo

docker nginx nginx-reverse-proxy nodejs reverse-proxy

Last synced: about 1 month ago
JSON representation

Setup and configure Nginx as Reverse Proxy.

• Host: GitHub
• URL: https://github.com/atkaridarshan04/nginx-reverseproxy-demo
• Owner: atkaridarshan04
• Created: 2024-11-16T18:45:37.000Z (about 2 months ago)
• Default Branch: main
• Last Pushed: 2024-11-16T20:19:43.000Z (about 2 months ago)
• Last Synced: 2024-11-16T20:23:15.059Z (about 2 months ago)
• Topics: docker, nginx, nginx-reverse-proxy, nodejs, reverse-proxy
• Language: HTML
• Homepage:
• Size: 262 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Nginx as Reverse Proxy Demo

This repository demonstrates how to configure **Nginx** as a reverse proxy (load balancer) for three backend applications running in Docker containers.

---

## Project Setup

1. **Clone the repository:**  

   ```bash

   git clone https://github.com/atkaridarshan04/Nginx-ReverseProxy-Demo.git

   ```

2. **Start the containerized backend applications:**  

   ```bash

   docker-compose up -d

   ```

3. **Test the containerized applications:**  

   Open the following URLs in your browser to verify the backend services:  

   - [http://localhost:3001](http://localhost:3001)  

   - [http://localhost:3002](http://localhost:3002)  

   - [http://localhost:3003](http://localhost:3003)

   ![docker-compose.png](./images/docker-compose.png)

---

## Installing Nginx

1. **Update your system and install Nginx:**  

   ```bash

   sudo apt update && sudo apt install nginx

   ```

2. **Check available Nginx options:**  

   ```bash

   nginx -h

   ```

3. **Start the Nginx service:**  

   ```bash

   nginx

   sudo systemctl start nginx

   ```

4. **Verify Nginx is running:**  

   Open [http://localhost:80](http://localhost:80) in your browser to see the default Nginx page.  

   ![nginx-default.png](./images/nginx-default.png)

---

## Configuring Nginx as a Reverse Proxy

1. **Remove the default configuration file:**  

   ```bash

   sudo rm /etc/nginx/nginx.conf

   ```

2. **Edit the Nginx configuration file:**  

   ```bash

   sudo vi /etc/nginx/nginx.conf

   ```

3. **Generate SSL certificates:**  

   Create a directory for Nginx certificates and generate a self-signed SSL certificate.  

   ```bash

   mkdir ~/nginx-certs

   cd ~/nginx-certs

   ```

   ```bash

   openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout nginx-selfsigned.key -out nginx-selfsigned.crt

   ```

   ![nginx-creds.png](./images/nginx-creds.png)

   **Note:** Adjust the certificate file paths in the Nginx configuration file ([nginx.conf](nginx.conf)) as per your setup.

4. **Paste the Nginx configuration file contents:**  

   Replace the contents of `/etc/nginx/nginx.conf` with the provided [`nginx.conf`](./nginx.conf) file.

5. **Restart Nginx to apply the configuration:**  

   ```bash

   nginx -s reload

   sudo systemctl restart nginx

   ```

6. **Access the reverse proxy:**  

   - [http://localhost:8080](http://localhost:8080)  

   - [https://localhost:443](https://localhost:443)  

   ![nginx-ssl-configured.png](./images/nginx-ssl-configured.png)  

   ![ssl-certificate.png](./images/ssl-certificate.png)  

   **Note:** As this is a self-signed SSL certificate, your browser may show a "not secure" warning. In production, use a valid SSL certificate to avoid warnings.

---

## Managing Nginx

### **View Logs**

To view the Nginx access logs:  

```bash

tail -f /usr/local/var/log/nginx/access.log

```

### **Stop Nginx**

To stop the Nginx service:  

```bash

nginx -s stop

```

---

## Additional Notes

- To edit the default Nginx index page:  

  ```bash

  sudo vi /var/www/html/index.nginx-debian.html

  ```

- Ensure that the self-signed certificates are used only in testing or development environments. In production, always use valid SSL certificates from trusted certificate authorities.

---