I’ve been at it for the whole day trying to work through this problem.
Seafile works without the reverse proxy in place, synced 4GB of data super fast.
The problem with the Synology is that it locks down ports 443 and 80 for it’s own Nginx RP server, so installing other systems can be a bit of a pain in the arse to configure (switching ports), and you may need to redo that work upon updates, so I’d rather get it configured for the existing software.
The problem with the existing reverse proxy interface is that they don’t allow for much in the way of configuration. You can add some stuff like ‘proxy_pass’, but you can’t add the location /seafhttp config settings.
I’ve ended up changing the nginx config file inside the synology - only problem is that if I open the control panel on synology, it reverts back to how it was before.
server {
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name {seafileURL};
ssl_certificate /usr/syno/etc/certificate/ReverseProxy/xxx/fullchain.pem;
ssl_certificate_key /usr/syno/etc/certificate/ReverseProxy/xxx/privkey.pem;
add_header Strict-Transport-Security "max-age=15768000; includeSubdomains; preload" always;
location / {
proxy_connect_timeout 12000;
proxy_read_timeout 12000;
proxy_send_timeout 12000;
proxy_intercept_errors off;
proxy_http_version 1.1;
proxy_set_header Host $http_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;
proxy_pass http://192.168.1.77:8000;
}
error_page 403 404 500 502 503 504 @error_page;
location @error_page {
root /usr/syno/share/nginx;
rewrite (.*) /error.html break;
allow all;
}
location /seafhttp {
rewrite ^/seafhttp(.*)$ $1 break ;
proxy_pass http://192.168.1.77:8082 ;
client_max_body_size 0;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_connect_timeout 36000s;
proxy_read_timeout 36000s;
proxy_send_timeout 36000s;
proxy_request_buffering off;
}
location /media {
root /opt/seafile/seafile-server-latest/seahub;
}
}