在nginx反向代理背后访问synology DSM

我试图访问我的synology nas web ui，在我的覆盆子上运行的nginx反向代理之后。 Nginx反向代理正在为其他的东西，像我的鬼博客。我复制/粘贴设置，通过nas.my.domain访问我的nas 192.168.0.123:5000，但是我find了“Synology / Sorry，找不到页面”而不是DSM的login提示。

这是我的nginx的设置

upstream nas { server 192.168.0.123:5001; # server 192.168.0.123:5000; KO # server 192.168.0.123; KO } server { listen 80; return 302 https://$server_name$request_uri; } server { server_name nas.my.domain; listen 443 ssl http2; # listen [::]:443 ssl http2; access_log /var/log/nginx/nas.access.log; error_log /var/log/nginx/nas.error.log; ssl_certificate /etc/letsencrypt/live/nas.my.domain/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/nas.my.domain/privkey.pem; include /etc/nginx/include/diffie-hellman; client_max_body_size 2m; location ~* \.(?:ico|css|js|gif|jpe?g|png|ttf|woff|)$ { access_log off; expires 30d; add_header Pragma public; add_header Cache-Control "public, mustrevalidate, proxy-revalidate"; proxy_pass https://nas; } location / { proxy_set_header HOST $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-NginX-Proxy true; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504; proxy_pass https://nas; proxy_redirect off; proxy_buffering off; } }

在NAS中，我使用nas.my.domain http = 80和https = 443设置了控制面板/外部访问/高级。

任何想法请修复或解决这个问题？

最好的祝福，

我设法得到它的工作，不知道为什么

只有端口443以某种方式反应

这是全白的，直到我把所有的标题从位置/到位置进行图像caching。

上游nas {server 192.168.0.123:443; }

服务器{听80; 返回302 https：// $ server_name $ request_uri; }

服务器{server_name nas.my.domain;

 listen 443 ssl http2; # listen [::]:443 ssl http2; access_log /var/log/nginx/nas.access.log; error_log /var/log/nginx/nas.error.log; ssl_certificate /etc/letsencrypt/live/nas.my.domain/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/nas.my.domain/privkey.pem; include /etc/nginx/include/diffie-hellman; client_max_body_size 2m; location ~* \.(?:ico|css|js|gif|jpe?g|png|ttf|woff|)$ { access_log off; expires 30d; add_header Pragma public; add_header Cache-Control "public, mustrevalidate, proxy-revalidate"; proxy_set_header HOST $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-NginX-Proxy true; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504; proxy_pass https://nas; proxy_redirect off; proxy_buffering off; } location / { proxy_set_header HOST $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-NginX-Proxy true; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504; proxy_pass https://nas; proxy_redirect off; proxy_buffering off; }

}