# Block 1: Redirects all HTTP traffic to HTTPS
server {
    listen 80;
    server_name notes.aaf.systems;

    # This redirect is managed by Certbot's --redirect flag, 
    # but we include it for completeness.
    return 301 https://$host$request_uri;
}

# Block 2: Handles the secure HTTPS traffic
server {
    listen 443 ssl http2;
    server_name notes.aaf.systems;

    # --- This is the location block that was missing ---
    location / {
        proxy_pass http://100.93.165.98:3010;
        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_set_header Host $host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
    # --- End of location block ---

    # SSL settings managed by Certbot
    ssl_certificate /etc/letsencrypt/live/git.aaf.systems/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/git.aaf.systems/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
}