Hello.
I have a nextcloudpi (pi4) Which is working fine.
I’m tryin access behind ngnix reverse proxy. But alway got 404, what is wrong?
Proxy server
dietpi@DietPi:~$ sudo tail -f /var/log/nginx/cloud.access.log
[16/Nov/2021:12:50:05 +0000] “GET / HTTP/1.1” 404 178 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36 Edg/95.0.1020.53”
Config:
server {
server_name ddns.com; access_log /var/log/nginx/cloud.access.log; error_log /var/log/nginx/cloud.error.log; client_max_body_size 0; underscores_in_headers on; location = /.well-known/cardav { rewrite ^ /index.php$uri; return 301 http://192.168.0.111/remote.php/dav; } location = /.well-known/caldav { rewrite ^ /index.php$uri; return 301 http://192.168.0.111/remote.php/dav; } location / { proxy_hide_header Upgrade; proxy_redirect off; proxy_headers_hash_max_size 512; proxy_headers_hash_bucket_size 64; proxy_set_header Host $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; rewrite ^ /index.php$uri; proxy_pass http://192.168.0.111; } location ~ \.php(?:$|/) { include snippets/fastcgi-php.conf; fastcgi_pass php; }
listen [::]:443 ssl ipv6only=on; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/ddns.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/ddns.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 Certbotadd_header Strict-Transport-Security "max-age=31536000" always; # managed by Certbot ssl_trusted_certificate /etc/letsencrypt/live/ddns.com/chain.pem; # managed by Certbot ssl_stapling on; # managed by Certbot ssl_stapling_verify on; # managed by Certbot
}
server {
return 301 https://$host$request_uri;
}