Telebox - error when uploading files

Suspected Bug
1

What is the problem you are having with rclone?

I used rclone for several months for everyday sync files to Telebox cloud. But at the end of a december rclone stopped storing files.

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

rclone v1.68.2-termux
- os/version: unknown
- os/kernel: 4.14.180-perf-g5d6f377 (aarch64)
- os/type: android
- os/arch: arm64 (ARMv8 compatible)
- go/version: go1.23.2
- go/linking: dynamic
- go/tags: noselfupdate

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

Telebox (Linkbox)

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

rclone copy test.pdf  telebox: --retries 1 -vv

The rclone config contents with secrets removed.

[telebox]
type = linkbox
token = token_from_www.linkbox.to/admin/account

A log from the command with the -vv flag

2025/01/05 09:13:22 DEBUG : rclone: Version "v1.68.2-termux" starting with parameters ["rclone" "copy" "test.pdf" "telebox:" "--retries" "1" "-vv"]
2025/01/05 09:13:22 DEBUG : Creating backend with remote "test.pdf"
2025/01/05 09:13:22 DEBUG : Using config file from "/data/data/com.termux/files/home/.config/rclone/rclone.conf"
2025/01/05 09:13:22 DEBUG : fs cache: adding new entry for parent of "test.pdf", "/data/data/com.termux/files/home"
2025/01/05 09:13:22 DEBUG : Creating backend with remote "telebox:"
2025/01/05 09:13:23 DEBUG : test.pdf: Need to transfer - File not found at Destination
2025/01/05 09:13:31 ERROR : test.pdf: Failed to copy: update err in uploading file: HTTP error 403 (403 Forbidden) returned body: "<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?><Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><RequestId>xxxxxxxxxxxxxxxxx</RequestId><HostId>xxxxxxxxxxxxxxxxx</HostId><AWSAccessKeyId>xxxxxxxxxxxxxxxx</AWSAccessKeyId><SignatureProvided>xxxxxxxxxxxxxxxxxxxx</SignatureProvided><StringToSign>PUT\n\n\nxxxxxxxxxxxx</StringToSign><StringToSignBytes>xx xx xx ... xx</StringToSignBytes></Error>"
2 Likes
2

The problem with loading new data and synchronizing information to the TeleBox cloud using RClone began in mid-November 2024. Reinstalling the program and updating it did not give any result. Data is not synchronized. The Crypt function does not work with the TeleBox cloud either.

1 Like
3

I also experience this problem. Does anyone has a solution for this?

1 Like
4

Unfortunately, synchronization with the TeleBox still doesn't work. Files are not loaded at all.

6

Hello @ncw , sorry for directly tag you here but do rclone have any solution for this issue or fixing in future update? And do it's needed any support from Telebox?

7

imho, all of you should contact telebox.

1 Like
8

I've submit the support sheet on their website but don't receive any answer and I can't find their support mail.

9

Yesterday I found that synchronization is already working. Seems the problem is fixed on the server side.

10

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