Nginx Configuration for Reverse Proxying to WordPress

I've identified a few issues in your Nginx configuration that might be causing problems with your reverse proxy setup. Here are the corrections and suggestions:

Issues in Your Configuration

1. There's a syntax error in your proxy_pass directive for the /route-name/ location. The URL is malformed.
2. You might need to specify the actual domain name of your WordPress site rather than just the IP address.
3. You may need additional proxy headers for WordPress to work correctly.

Corrected Configuration

Here's a corrected version of your Nginx configuration:

NGINXCopied
server {
    # Server name should be defined at the top
    server_name example.com www.example.com;

    location = /favicon.ico { access_log off; log_not_found off; }

    location /static/ {
        alias /var/www/example.com/static/;
    }

    location /media/ {
        alias /var/www/example.com/media/;
    }

    # Reverse proxy for /route-name
    location /route-name/ {
        # Fix the URL format - ensure there's no trailing slash after the IP/domain
        proxy_pass http://wordpress-domain-or-ip-address;
        
        # Set the correct Host header for the WordPress site
        proxy_set_header Host wordpress-domain-or-ip-address;
        
        # Additional headers that might be needed
        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;
        
        # Increase timeouts if needed
        proxy_connect_timeout 60s;
        proxy_read_timeout 60s;
        
        # Handle redirects properly
        proxy_redirect off;
    }

    location / {
        include proxy_params;
        proxy_redirect off;
        proxy_pass http://unix:/run/gunicorn.sock;
    }

    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}

server {
    if ($host = www.example.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    if ($host = example.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    listen 80 default_server;
    listen [::]:80 default_server;
    server_name example.com www.example.com;
    return 404; # managed by Certbot
}

Key Changes

1. Fixed the proxy_pass URL format
2. Added the Host header with the actual WordPress domain
3. Added X-Forwarded-Proto header which is important for SSL
4. Added timeout settings to handle potential delays
5. Moved the server_name directive to the top for better readability

After making these changes, restart Nginx with:

BASHCopied
sudo nginx -t       # Test the configuration
sudo systemctl restart nginx  # Apply the changes

If you're still having issues, check your Nginx error logs for more specific information:

BASHCopied
sudo tail -f /var/log/nginx/error.log