Head requests fails using uppy with tusd

Uppy
1

Hey,
I’m currently in somewhat of a desperate situation, as I can’t get a hold of a problem in my application.

General setup:

"@uppy/core": "^4.2.3",
"@uppy/dashboard": "^4.1.2",
"@uppy/drag-drop": "^4.0.4",
"@uppy/progress-bar": "^4.0.1",
"@uppy/status-bar": "^4.0.4",
"@uppy/tus": "^4.1.3",

tusd 2.5.0

tusd is running behind a nginx.
config:

location /files/ {
        rewrite ^/files/(.*) $scheme://$http_host/tusd/files/$1 last;
    }

    location /tusd {
        rewrite ^/tusd/(.*) /$1 break;
        proxy_pass $tusdStream;

        proxy_request_buffering  off;
        proxy_buffering          off;
        proxy_http_version       1.1;
        # Add X-Forwarded-* headers
        proxy_set_header X-Forwarded-Host $http_host;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        client_max_body_size        0;
        proxy_pass_request_headers  on;
    }

Uppy config:

uppy.use(Tus, {
    endpoint: '/tusd/files/',
    chunkSize: 4194304,
    headers: {
        "Authorization": "Bearer " + UPLOAD_TOKEN
    },
    limit: 3,
    removeFingerprintOnSuccess: true,
    retryDelays: [0, 1000, 3000, 5000],
    storeFingerprintForResuming: true,
});

Now the problem:
User(s) is trying to upload a file on the client side, I’m getting the first request but afterwards it aborts immediately.
Strange thing about this is, that it’s not happening for all users and for some it works again after they switched the browser.
First I thought it would a be caching issue, but as a user experienced the problem even though he was newly created, I’m a bit confused now…
I took a look at the logs and saw that we have "message": "Client error", and UploadClientError there.
But not really anything that gives a message of what the error actually is.
For example:

"progress": {
            "percentage": 0,
            "bytesUploaded": false,
            "bytesTotal": 2522,
            "uploadComplete": false,
            "uploadStarted": null
          },
          "size": 2522,
          "isGhost": false,
          "isRemote": false
        },
        "error": {
          "originalRequest": {
            "_xhr": [],
            "_method": "HEAD",
...
  },
          "originalResponse": null,
          "causingError": []
        }
      }
    }
  },
  "level": 400,
  "level_name": "ERROR",

They’re all related to the head request and it seems it’s not uploading anything in the end, as the files are also 0 bytes.

I tried to recreate the problem on my setup(s) as well but wasn’t able to.
Neither different Browsers, nor caching weird situations or anything.

Does someone have a clue what might be going on?
I already requested a screenshot from affected users, but still waiting for a response.

Thanks a lot!

3

As mentioned here:

we think it could be an issue with the way uppy addresses local storage, as the exception shown to the user is

QuotaExceededError: Failed to execute 'setitem' on 'Storage':

maybe someone else already had a similar problem?