Unable to upload to mega:

STOP and READ USE THIS TEMPLATE NO EXCEPTIONS - By not using this, you waste your time, our time and really hate puppies. Please remove these two lines and that will confirm you have read them.

What is the problem you are having with rclone?

The following command does not run succsessfully.

rclone -vvv sync -L --exclude-from /home/stuart/utilities/rclone_excludefromhome.txt /home/stuart/ mega:

I have been using this same command for years and it has worked fine.

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

rclone v1.70.3
  • os/version: arch (64 bit)
  • os/kernel: 6.15.6-arch1-1 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.24.5
  • go/linking: dynamic
  • go/tags: none

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

mega.nz

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

rclone -vvv sync -L --exclude-from /home/stuart/utilities/rclone_excludefromhome.txt /home/stuart/ mega:

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

Current remotes:

Name                 Type
====                 ====
dropbox              dropbox
google               drive
google_secret        crypt
mega                 mega
onedrive             onedrive
onedrive_secret      crypt

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q> ^[[A^[[A^[[A^[[B^Z
[3]+  Stopped                    rclone config
[stuart@archlinux ~]$ rclone config redacted
[dropbox]
type = dropbox
token = XXX
client_id = XXX
client_secret = XXX

[google]
type = drive
client_id = XXX
client_secret = XXX
scope = drive
token = XXX
root_folder_id = XXX

[google_secret]
type = crypt
remote = google:
filename_encryption = standard
directory_name_encryption = false
password = XXX
password2 = XXX

[mega]
type = mega
user = XXX
pass = XXX

[onedrive]
type = onedrive
token = XXX
drive_id = XXX
drive_type = personal
client_id = 
client_secret = 

[onedrive_secret]
type = crypt
remote = onedrive:
directory_name_encryption = false
password = XXX
password2 = XXX

A log from the command that you were trying to run with the -vv flag

2025/07/16 16:51:07 ERROR : car/113194459_1_NCD_Information_Sheet.pdf: Failed to copy: failed to finish upload: Invalid arguments
2025/07/16 16:51:08 ERROR : car/113194459_1_PDS_Part_B.pdf: Failed to copy: failed to finish upload: Invalid arguments
2025/07/16 16:51:08 ERROR : car/113194459_1_Renewal_Offer.pdf: Failed to copy: failed to finish upload: Invalid arguments
2025/07/16 16:51:09 ERROR : car/Car_Supplementary_PDS_Budget_Direct_November2024.pdf: Failed to copy: failed to finish upload: Invalid arguments
2025/07/16 16:51:09 ERROR : budgets/Woolworth's Orders.ods: Failed to copy: failed to finish upload: Invalid arguments
2025/07/16 16:51:10 ERROR : budgets/electricity and gas costs-2025.xlsx: Failed to copy: failed to finish upload: Invalid arguments

1 Like

hi,
can you rclone copy a single file and post the full debug log.

Many thanks for taking the time to help.

Details requested are as follows:
rclone -vvv copy -L /home/stuart/rclone-config.txt mega:2025/07/17 13:32:40 DEBUG : rclone: Version "v1.70.3" starting with parameters ["rclone" "-vvv" "copy" "-L" "/home/stuart/rclone-config.txt" "mega:"]
2025/07/17 13:32:40 DEBUG : Creating backend with remote "/home/stuart/rclone-config.txt"
2025/07/17 13:32:40 DEBUG : Using config file from "/home/stuart/.config/rclone/rclone.conf"
2025/07/17 13:32:40 DEBUG : local: detected overridden config - adding "{12rtk}" suffix to name
2025/07/17 13:32:40 DEBUG : fs cache: renaming child cache item "/home/stuart/rclone-config.txt" to be canonical for parent "local{12rtk}:/home/stuart"
2025/07/17 13:32:40 DEBUG : Creating backend with remote "mega:"
2025/07/17 13:32:45 DEBUG : rclone-config.txt: Need to transfer - File not found at Destination
2025/07/17 13:32:46 ERROR : rclone-config.txt: Failed to copy: failed to finish upload: Invalid arguments
2025/07/17 13:32:46 ERROR : Attempt 1/3 failed with 1 errors and: failed to finish upload: Invalid arguments
2025/07/17 13:32:46 DEBUG : rclone-config.txt: Need to transfer - File not found at Destination
2025/07/17 13:32:47 ERROR : rclone-config.txt: Failed to copy: failed to finish upload: Invalid arguments
2025/07/17 13:32:47 ERROR : Attempt 2/3 failed with 1 errors and: failed to finish upload: Invalid arguments
2025/07/17 13:32:47 DEBUG : rclone-config.txt: Need to transfer - File not found at Destination
2025/07/17 13:32:48 ERROR : rclone-config.txt: Failed to copy: failed to finish upload: Invalid arguments
2025/07/17 13:32:48 ERROR : Attempt 3/3 failed with 1 errors and: failed to finish upload: Invalid arguments
2025/07/17 13:32:48 INFO :
Transferred: 1.125 KiB / 1.125 KiB, 100%, 383 B/s, ETA 0s
Errors: 1 (retrying may help)
Elapsed time: 3.4s

2025/07/17 13:32:48 DEBUG : 12 go routines active
2025/07/17 13:32:48 NOTICE: Failed to copy: failed to finish upload: Invalid arguments

FYI

I have noticed lately similar behaviour on one of my mega test accounts:

2025/07/17 03:35:04 ERROR : data/03/03598aae57b3ddd627ed76681baf316c26505d0b7fd2b39e6dc99ab39b6c0623: Failed to copy: failed to finish upload: Invalid arguments
...
2025/07/17 03:55:09 ERROR : Attempt 1/3 failed with 64 errors and: failed to finish upload: Invalid arguments
...
2025/07/17 03:55:23 ERROR : data/03/03598aae57b3ddd627ed76681baf316c26505d0b7fd2b39e6dc99ab39b6c0623: Failed to copy: failed to finish upload: Invalid arguments
...
2025/07/17 03:58:38 ERROR : Attempt 2/3 failed with 11 errors and: failed to finish upload: Invalid arguments
2025/07/17 03:59:29 ERROR : Attempt 3/3 succeeded

But in my case it usually succeeds eventually (like in an example above).

Clearly "Invalid arguments" error is misleading as it does not have anything to do with rclone command I think.

1 Like

I'm seeing the same issue on my end despite never having changed my config.

Output of rclone config show mega:

[mega]
type = mega
user = <redacted>
pass = *** ENCRYPTED ***

Output of rclone --version:

rclone v1.70.3
- os/version: debian 13.0 (64 bit)
- os/kernel: 6.12.37+deb13-amd64 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.24.4
- go/linking: static
- go/tags: none

Although the issue is likely agnostic to a recent change in rclone itself, as I initially encountered this issue today while running an old version of rclone, v1.64.0, upgraded to v1.70.3 while troubleshooting, and encountered the same error.

I'm able to copy existing files from the remote to my local machine. And I can create files via the MEGA web UI, for example, example.txt at the root of my directory, and successfully copy it with:
rclone copy mega:example.txt .

But uploading fails. For example:

echo "upload" > upload.txt
rclone copy -v upload.txt mega:

Produces:

2025/07/17 00:22:38 ERROR : upload.txt: Failed to copy: failed to finish upload: Invalid arguments
2025/07/17 00:22:38 ERROR : Attempt 1/3 failed with 1 errors and: failed to finish upload: Invalid arguments
2025/07/17 00:22:38 ERROR : upload.txt: Failed to copy: failed to finish upload: Invalid arguments
2025/07/17 00:22:38 ERROR : Attempt 2/3 failed with 1 errors and: failed to finish upload: Invalid arguments
2025/07/17 00:22:39 ERROR : upload.txt: Failed to copy: failed to finish upload: Invalid arguments
2025/07/17 00:22:39 ERROR : Attempt 3/3 failed with 1 errors and: failed to finish upload: Invalid arguments
2025/07/17 00:22:39 INFO  : 
Transferred:   	        21 B / 21 B, 100%, 0 B/s, ETA -
Errors:                 1 (retrying may help)
Elapsed time:         1.2s

2025/07/17 00:22:39 NOTICE: Failed to copy: failed to finish upload: Invalid arguments

Retrying produces the same error. I'm unable to upload anything to my mega remote via the rclone CLI. I regularly use rclone with this remote and I've used this setup for years without any problems, so I'm confident this is a recent issue.

Any help is greatly appreciated!

It is interesting because for me retrying always works at the end.

In my case it is also setup which worked flawlessly before.

The issue does not happen every time. At the moment it looks like totally random.