der Reversproxy

Folgender Code muss für einen neuen Server angepasst werden

server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;

        server_name web.ecn-dev.de;
        set $upstream 192.168.236.193;
        ssl_certificate /etc/letsencrypt/live/pve1.ecn-dev.de/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/pve1.ecn-dev.de/privkey.pem;
        ssl_session_timeout 1d;
        ssl_session_cache shared:MozSSL:10m;
        ssl_session_tickets off;
        ssl_protocols TLSv1.3 TLSv1.2;
        ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
        ssl_prefer_server_ciphers off;
        add_header Strict-Transport-Security "max-age=63072000" always;
        ssl_stapling on;
        ssl_stapling_verify on;

        access_log /var/log/nginx/access.log;
        client_max_body_size 0;

        location / {
                client_max_body_size 512M;
                proxy_pass http://$upstream;
                proxy_set_header Connection $http_connection;
                proxy_set_header Upgrade $http_upgrade;
                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;
                }
}

hier sind die Zeilen 5 und 6 auf jeweiligen Begebenheiten anzupassen!