filebrowser icon indicating copy to clipboard operation
filebrowser copied to clipboard

Published 20 hours ago • verified publisher icon filebrowser

Error when uploading files

Open antonio1475 opened this issue 2 years ago • 10 comments

Description Uploading a file from Windows via Chrome results in error

Expected behaviour File is uploaded as normal

What is happening instead? File is created with the name, but empty.

Upload failed: Error: tus: unable to resume upload (new upload cannot be created without an endpoint), originated from request (method: HEAD, url: /api/hassio_ingress/pI_Ipm6K_ZuHCMhvhilVO9yXOYExMe9VOmsvi8eB3Gg/api/tus/config/www/Ticket.To.Paradise.en.txt?override=false, response code: 405, response text: , request id: n/a)

Additional context image

How to reproduce?

  1. Go to folder in Filebrowser
  2. Click upload icon
  3. Select file in Windows file browser, click Upload
  4. See error (file is created).

Drag&drop from Windows results in the same error.

Files Ticket.To.Paradise.en.txt

antonio1475 avatar Sep 16 '23 12:09 antonio1475

Probably a duplicate of https://github.com/filebrowser/filebrowser/issues/2712 Apologies, the Report bug button took me directly to opening an issue without checking first for existing ones...

antonio1475 avatar Sep 16 '23 12:09 antonio1475

Seeing this as well.

bcutter avatar Sep 22 '23 08:09 bcutter

Hi, same as https://github.com/filebrowser/filebrowser/issues/2712 : homeassistant embedded proxy is not compatible with TUS. As I can't change homeassistant I've reverted the addon version and it should work again

alexbelgium avatar Oct 14 '23 12:10 alexbelgium

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Nov 14 '23 01:11 github-actions[bot]

I've opened a request for an optional setting to disable TUS otherwise we should just stay on the previous version (but affected by the CSS bug preventing refresh on modern browsers)

alexbelgium avatar Nov 14 '23 06:11 alexbelgium

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Dec 15 '23 01:12 github-actions[bot]

A downgrade is no permanent solution, we need to keep this open until the noted request is (hopefully) implemented.

bcutter avatar Dec 15 '23 07:12 bcutter

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Jan 15 '24 01:01 github-actions[bot]

Not stale

alexbelgium avatar Jan 15 '24 08:01 alexbelgium

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

github-actions[bot] avatar Feb 16 '24 01:02 github-actions[bot]

This issue was closed because it has been stalled for 5 days with no activity.

github-actions[bot] avatar Feb 22 '24 01:02 github-actions[bot]