Linkbox upload error

Suspected Bug
1

What is the problem you are having with rclone?

I am trying to upload a file (myvideo.mp4) to Linkbox using rclone but I keep getting the error: Failed to copy: Failed to copy: Update second step failed: Linkbox error 500: user upload file not exist
I also get HTTP error 522 sometimes when trying retries. I tried using the official Linkbox API for uploading as well, but I get the same response repeatedly.

Run the command 'rclone version' and share the full output of the command.

D:\rclone-v1.70.2-windows-amd64>rclone version
rclone v1.70.2

  • os/version: Microsoft Windows 10 Pro 22H2 22H2 (64 bit)
  • os/kernel: 10.0.19045.6036 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.24.4
  • go/linking: static
  • go/tags: cmount

Which cloud storage system are you using? (eg Google Drive)

Linkbox Cloud Storage

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone copy myvideo.mp4 linkbox:/

The rclone config contents with secrets removed.

[linkbox]
type = linkbox
token = [REDACTED]

A log from the command with the -vv flag

2025/07/03 14:24:53 DEBUG : rclone: Version "v1.70.2" starting with parameters ["rclone" "copy" "myvideo.mp4" "linkbox:/" "-vv"]
2025/07/03 14:24:53 DEBUG : Creating backend with remote "myvideo.mp4"
2025/07/03 14:24:53 DEBUG : Using config file from "C:\\Users\\bilal\\AppData\\Roaming\\rclone\\rclone.conf"
2025/07/03 14:24:53 DEBUG : fs cache: renaming child cache item "myvideo.mp4" to be canonical for parent "//?/D:/rclone-v1.70.2-windows-amd64"
2025/07/03 14:24:53 DEBUG : Creating backend with remote "linkbox:/"
2025/07/03 14:24:53 DEBUG : fs cache: renaming cache item "linkbox:/" to be canonical "linkbox:"
2025/07/03 14:24:54 DEBUG : myvideo.mp4: Need to transfer - File not found at Destination
2025/07/03 14:24:57 ERROR : myvideo.mp4: Failed to copy: Update second step failed: Linkbox error 500: user upload file not exist
2025/07/03 14:24:57 ERROR : Attempt 1/3 failed with 1 errors and: Update second step failed: Linkbox error 500: user upload file not exist
2025/07/03 14:24:57 DEBUG : myvideo.mp4: Need to transfer - File not found at Destination
2025/07/03 14:25:00 ERROR : myvideo.mp4: Failed to copy: Update second step failed: Linkbox error 500: user upload file not exist
2025/07/03 14:25:00 ERROR : Attempt 2/3 failed with 1 errors and: Update second step failed: Linkbox error 500: user upload file not exist
2025/07/03 14:25:00 DEBUG : myvideo.mp4: Need to transfer - File not found at Destination
2025/07/03 14:25:02 ERROR : myvideo.mp4: Failed to copy: Update second step failed: Linkbox error 500: user upload file not exist
2025/07/03 14:25:02 ERROR : Attempt 3/3 failed with 1 errors and: Update second step failed: Linkbox error 500: user upload file not exist
2025/07/03 14:25:02 INFO  :
Transferred:       15.899 MiB / 15.899 MiB, 100%, 1.767 MiB/s, ETA 0s
Errors:                 1 (retrying may help)
Elapsed time:         8.7s

2025/07/03 14:25:02 DEBUG : 3 go routines active
2025/07/03 14:25:02 NOTICE: Failed to copy: Update second step failed: Linkbox error 500: user upload file not exist

I also tried using the official Linkbox API for uploading, but I get the same response every time.

What I have tried so far:

  • Checked the file exists locally.
  • Verified my Linkbox remote is configured correctly in rclone.
  • Tried multiple upload attempts.
  • Tried the official Linkbox API manually.

I would appreciate any guidance on:

  • What this error means exactly.
  • How to fix it or troubleshoot further.
  • Whether there is something wrong with my rclone configuration or with the API usage.

Thank you in advance for your help!

2

welcome to the forum,

if that is true, then this is not a rclone bug, correct?

https://forum.rclone.org/t/failed-to-copy-update-second-step-failed-linkbox-error-500-user-upload-file-not-exist/51604

3

However, if the file:

  • already exists in Linkbox, rclone successfully uploads it by renaming it (e.g., adds (1)),
  • previously existed but was deleted from Linkbox, the upload also succeeds.

So the problem only occurs for completely new files that were never present before.

I also tried using the official Linkbox API manually but got the same 500 error response.

It seems like the Linkbox backend in rclone is not properly initializing uploads for new files, or the file entry is not being registered on the server during the first step.

4

so, that has nothing to do with rclone, correct?

5

That's a very good point — and I agree that it seems to be an issue on Linkbox's side, most likely related to how their API handles new uploads.

I still wanted to report it here in case:

  • Someone else runs into the same issue and is looking for answers,
  • Or if there's any chance that rclone could apply a workaround, log it more clearly, or confirm it's handling the upload steps correctly from its side.

Thanks again for your time and feedback!

6

it has already been reported.

7

Thanks for the heads-up! I wasn't aware it had already been reported, I appreciate the link. Hopefully Linkbox addresses the issue soon.

8

@Bilal_mabo these errors are also occurring in the daily integration tests and have been for some time.

Can you open a new issue on Github about this please and we can get see if we can put a workaround into rclone - thanks

1 Like
9

@Bilal_mabo don't open an issue there is one already linked above!

I did have a look at this - please give this a go

v1.71.0-beta.8843.52081eb2b.fix-linkbox-upload on branch fix-linkbox-upload (uploaded in 15-30 mins)

1 Like
10

I’ve tested the build, and the upload is working perfectly now. Thanks a lot for taking the time to investigate and resolve the problem!

1 Like
11

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.