Upload link doesn't work

Hello,
I am using the latest version of Seafile pro server (6.1.4) and I am having a problem.

I have generated an upload link for a library. Whenever someone tries to upload something, it will not upload. It shows uploading status without any percentage change. Small files upload fine. Larger files stay like this.

See the attached picture

Can someone help me troubleshoot? It worked fine with previous versions.
Thank you

Nginx vhost config:
server {
listen 80;
server_name files.domain.com;
return 301 https://$server_name$request_uri;
}

server {
listen 443 ssl http2;
ssl on;
ssl_certificate /etc/letsencrypt/live/files.domain.com/fullchain.pem; # path to your cacert.pem
ssl_certificate_key /etc/letsencrypt/live/files.domain.com/privkey.pem; # path to your privkey.pem
include /etc/letsencrypt/options-ssl-nginx.conf;
server_name files.domain.com;
proxy_set_header X-Forwarded-For $remote_addr;

    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains";
    server_tokens off;

    location / {
        fastcgi_pass    127.0.0.1:8000;
        fastcgi_param   SCRIPT_FILENAME     $document_root$fastcgi_script_name;
        fastcgi_param   PATH_INFO           $fastcgi_script_name;

        fastcgi_param   SERVER_PROTOCOL        $server_protocol;
        fastcgi_param   QUERY_STRING        $query_string;
        fastcgi_param   REQUEST_METHOD      $request_method;
        fastcgi_param   CONTENT_TYPE        $content_type;
        fastcgi_param   CONTENT_LENGTH      $content_length;
        fastcgi_param   SERVER_ADDR         $server_addr;
        fastcgi_param   SERVER_PORT         $server_port;
        fastcgi_param   SERVER_NAME         $server_name;
        fastcgi_param   REMOTE_ADDR         $remote_addr;
        fastcgi_param   HTTPS               on;
        fastcgi_param   HTTP_SCHEME         https;

        access_log      /var/log/nginx/seahub.access.log;
        error_log       /var/log/nginx/seahub.error.log;
        fastcgi_read_timeout 36000;
        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_connect_timeout  36000s;
        proxy_read_timeout  36000s;
        proxy_send_timeout  36000s;
        send_timeout  36000s;
    }
    location /media {
        root /var/www/files.domain.com/seafile-server-latest/seahub;
    }
location /seafdav {
    fastcgi_pass    127.0.0.1:8080;
    fastcgi_param   SCRIPT_FILENAME     $document_root$fastcgi_script_name;
    fastcgi_param   PATH_INFO           $fastcgi_script_name;

    fastcgi_param   SERVER_PROTOCOL     $server_protocol;
    fastcgi_param   QUERY_STRING        $query_string;
    fastcgi_param   REQUEST_METHOD      $request_method;
    fastcgi_param   CONTENT_TYPE        $content_type;
    fastcgi_param   CONTENT_LENGTH      $content_length;
    fastcgi_param   SERVER_ADDR         $server_addr;
    fastcgi_param   SERVER_PORT         $server_port;
    fastcgi_param   SERVER_NAME         $server_name;
    fastcgi_param   HTTPS               on;
    fastcgi_param   HTTP_SCHEME         https;

    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;
}

}

seafile.log

[07/17/2017 08:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.

[07/17/2017 09:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 10:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 11:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 12:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 01:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 02:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 03:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 04:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 05:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 06:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 07:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 08:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 09:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 10:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/17/2017 11:47:25 PM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 12:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 01:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 02:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 03:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 04:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 05:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 06:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 07:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 08:47:25 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 09:46:59 AM] Disconnected from daemon
[07/18/2017 09:47:12 AM] …/common/mq-mgr.c(61): [mq client] mq cilent is started
[07/18/2017 09:47:12 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 10:13:15 AM] Disconnected from daemon
[07/18/2017 10:13:22 AM] …/common/mq-mgr.c(61): [mq client] mq cilent is started
[07/18/2017 10:13:22 AM] filelock-mgr.c(917): Cleaning expired file locks.
[07/18/2017 10:22:27 AM] …/common/mq-mgr.c(61): [mq client] mq cilent is started
[07/18/2017 10:22:27 AM] filelock-mgr.c(917): Cleaning expired file locks.

1 Like

We’re having the same issue with version 6.1.3 still.

Maybe it was the same for me. I haven’t tested this feature when I was on 6.1.3. Any fix from developers?

It works with chrome here and fails with firefox. Developer console shows 403 access forbidden. I think it happens when chunked upload should be used, thus very small files still work.

@daniel.pan

It doesn’t work for me in firefox and chrome.

I can’t reproduce the problem on demo.seafile.com with 6.1.14 pro. You can try the link: https://demo.seafile.com/u/d/0ef4199e09e445448dc1/

This seems to be a bug when resumable upload is turn on.

1 Like

Yes, disabling resumable uploads fixes the issue. I disabled it for now. Hopefully it will be fixed in the next version.

1 Like

Hi,

I can confirm it, too. :slight_smile:

@daniel.pan: Thank you for investigating.

Best regards

Thomas

This will be fixed in v6.1.7 pro.

Any ETA?