# REFERENTIE ALLEEN — dit bestand hoef je niet handmatig te kopiëren.
#
# Dit toont hoe /etc/nginx/sites-available/slpsoftware-analytics.conf op de
# reverse-proxy-Pi er automatisch uit komt te zien NADAT je certbot hebt
# gedraaid (`sudo certbot --nginx -d analytics.slpsoftware.nl`) op basis van
# analytics-nginx.conf.example. Certbot voegt zelf de HTTPS-configuratie en
# het HTTP→HTTPS-redirect-blok toe (herkenbaar aan de "managed by Certbot"
# commentaren), en zet de error_log/access_log en het proxy_pass-blok gewoon
# over naar het nieuwe HTTPS-serverblok.
server {

    server_name analytics.slpsoftware.nl;

    error_log /var/log/nginx/slpsoftware-analytics_error.log;
    access_log /var/log/nginx/slpsoftware-analytics_access.log;

    location /.well-known/acme-challenge/ {
        root /var/www/certbot;
    }

    location / {
        proxy_pass http://192.168.1.103:3001;

        proxy_set_header Host $host;
        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;
    }

    listen 443 ssl; # managed by Certbot
    listen [::]:443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/analytics.slpsoftware.nl/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/analytics.slpsoftware.nl/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 = analytics.slpsoftware.nl) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    listen 80;
    listen [::]:80;

    server_name analytics.slpsoftware.nl;
    return 404; # managed by Certbot
}