Hi.
I am trying to share some folder with upload rights to someone. Link created successfully but when I try to upload file by this link I am receiving “network error”. When I’ve tried to do the same with chrome development tools I see that firstly browser tried to go to some https link and then to the unsecured http port 8082, second operation fails.
Server 7.1.4, browser Chrome.
Nginx config:
cat /etc/nginx/conf.d/seafile.conf
server {
server_name *******; # managed by Certbot
root /usr/share/nginx/html;
# Load configuration files for the default server block.
include /etc/nginx/default.d/*.conf;
#TRICK FOR CORRECT WORKING OF SVNs COPY and MV METHODS READ MORE HERE: http://mailman.nginx.org/pipermail/nginx-ru/2016-August/058844.html
set $fixed_destination $http_destination;
if ($http_destination ~* ^https(?<foo>.*)$)
{
set $fixed_destination http$foo;
}
#TRICK FOR CORRECT WORKING OF SVNs COPY and MV METHODS
client_max_body_size 10G; # for uploading big files to the SVN server
location / {
proxy_pass http://127.0.0.1:8000;
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-Host $server_name;
proxy_set_header X-Forwarded-Proto https;
access_log /var/log/nginx/seahub.access.log;
error_log /var/log/nginx/seahub.error.log;
proxy_read_timeout 1200s;
client_max_body_size 0;
}
location /seafhttp {
rewrite ^/seafhttp(.*)$ $1 break;
proxy_pass http://127.0.0.1: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;
send_timeout 36000s;
proxy_request_buffering off;
}
location /media {
root /home/kt368/seafile/seafile-server-latest/seahub;
}
location /seafdav {
proxy_pass http://127.0.0.1:8080/seafdav;
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-Host $server_name;
proxy_set_header X-Forwarded-Proto $scheme;
client_max_body_size 0;
proxy_connect_timeout 36000s;
proxy_read_timeout 36000s;
proxy_send_timeout 36000s;
send_timeout 36000s;
# This option is only available for Nginx >= 1.8.0. See more details below.
proxy_request_buffering off;
access_log /var/log/nginx/seafdav.access.log;
error_log /var/log/nginx/seafdav.error.log;
}
error_page 404 /404.html;
location = /40x.html {
}
error_page 500 502 503 504 /50x.html;
location = /50x.html {
}
location /repos {
proxy_pass http://127.0.0.1:83/repos/;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Destination $fixed_destination;
}
listen [::]:443 ssl ipv6only=on; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/*******/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/*******/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
}
Do files will sent securely? Is it okay, that browser tried to use unsecured http connection? How to fix it?