CodeWithAbdessamad

Reverse Proxy

Deploying Applications: Reverse Proxy

When your applications need to handle high traffic, secure connections, or manage multiple services, a reverse proxy becomes your essential gateway. In this section, we’ll explore how to deploy a robust reverse proxy using Nginx on your VPS—perfect for Docker environments. This setup shields your containers from direct exposure, optimizes performance, and simplifies traffic routing. Let’s dive in.

Nginx Setup

Nginx is the industry-standard reverse proxy for modern web infrastructure. Its lightweight architecture, high concurrency handling, and extensive features make it ideal for Dockerized applications. Here’s how to set it up on your VPS:

  1. Install Nginx

First, ensure Nginx is installed on your VPS (most distributions have preconfigured Docker support):

<code class="language-bash">   # Ubuntu/Debian</p>
<p>   sudo apt update && sudo apt install nginx</p>

<p>   # CentOS/RHEL</p>
<p>   sudo dnf install nginx</code>

  1. Create a Reverse Proxy Configuration

We’ll set up a simple proxy for a Dockerized Flask app running on port 5000. This configuration handles SSL termination, path-based routing, and health checks:

<code class="language-nginx">   # /etc/nginx/conf.d/proxy.conf</p>
<p>   server {</p>
<p>       listen 80;</p>
<p>       server<em>name </em>;  # Wildcard for testing</p>

<p>       location / {</p>
<p>           proxy_pass http://flask-app:5000;  # Docker container name:port</p>
<p>           proxy<em>set</em>header Host $host;</p>
<p>           proxy<em>set</em>header X-Real-IP $remote_addr;</p>
<p>           proxy<em>set</em>header X-Forwarded-For $proxy<em>add</em>x<em>forwarded</em>for;</p>
<p>           proxy<em>set</em>header X-Forwarded-Proto $scheme;</p>
<p>       }</p>

<p>       # Health check for your container</p>
<p>       location /health {</p>
<p>           proxy_pass http://flask-app:5000/health;</p>
<p>       }</p>
<p>   }</code>

  1. Test and Reload Nginx

Verify the configuration and apply changes:

<code class="language-bash">   sudo nginx -t  # Check for syntax errors</p>
<p>   sudo systemctl reload nginx</code>

Why this works: The proxy_pass directive routes traffic to your Docker container (using the container’s name from the Docker network), while headers like X-Real-IP help your app track the client’s true IP. The health check endpoint ensures automatic failover if your container crashes.

💡 Pro Tip: Always use Docker’s network naming convention (flask-app) to avoid conflicts. Nginx will resolve this name automatically via Docker’s internal DNS.

Routing Domains

Once your reverse proxy is live, routing multiple domains becomes trivial. This is critical for hosting multiple applications under one VPS—like app1.example.com and app2.example.com—each pointing to different Docker services.

  1. Create Domain-Specific Server Blocks

In your Nginx configuration, add separate server blocks for each domain:

<code class="language-nginx">   # /etc/nginx/conf.d/domains.conf</p>
<p>   server {</p>
<p>       listen 80;</p>
<p>       server_name app1.example.com;  # Domain 1</p>

<p>       location / {</p>
<p>           proxy_pass http://app1-container:8080;  # Docker container name:port</p>
<p>           proxy<em>set</em>header Host $host;</p>
<p>       }</p>
<p>   }</p>

<p>   server {</p>
<p>       listen 80;</p>
<p>       server_name app2.example.com;  # Domain 2</p>

<p>       location / {</p>
<p>           proxy_pass http://app2-container:3000;  # Docker container name:port</p>
<p>           proxy<em>set</em>header Host $host;</p>
<p>       }</p>
<p>   }</code>

  1. Configure DNS Records

Point your domain names to your VPS’s public IP via DNS providers (e.g., Cloudflare, Route53). This ensures traffic reaches Nginx.

  1. Handle SSL (Optional but Recommended)

For production, enable SSL using Let’s Encrypt:

<code class="language-bash">   sudo apt install certbot</p>
<p>   sudo certbot --nginx -d app1.example.com -d app2.example.com</code>

This auto-issues SSL certificates and configures HTTPS for both domains.

Key Benefits of Domain Routing:

  • Isolation: Each domain operates independently without affecting others.
  • Scalability: Add new domains without changing Nginx core configuration.
  • Security: SSL terminates at Nginx, keeping sensitive data out of your Docker containers.
Domain Docker Container Port Use Case
app1.example.com app1-container 8080 API-heavy microservice
app2.example.com app2-container 3000 Real-time frontend

🔍 Troubleshooting Tip: If a domain doesn’t route, check DNS records first—Nginx only processes traffic after DNS resolves to your VPS. Also, verify container names match exactly (case-sensitive in Docker).

Summary

This section covered the core of reverse proxy deployment for Docker environments: starting with a basic Nginx setup for traffic routing and progressing to domain-specific routing. By leveraging Nginx’s flexibility, you can securely expose multiple Docker services under a single VPS while maintaining performance and scalability. Remember to always test configurations before production deployment—your apps will thank you! 🐳