Rclone and Mega error “failed to create file system”


I would be extremely grateful for your help.

What is the problem you are having with rclone?

I am trying to use rclone with my account at Mega, in my Linux system (Manjaro). It was installed succesfully, but I can't make it run properly.

When I try to see the contents of my remote (rclone ls Mega:), where "Mega" is the name I gave to it, I receive the below error:

Failed to create file system for "Mega:": couldn't login: Object (typically, node or user) not found

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

rclone --version
rclone v1.61.1
- os/version: arch 22.0.1 (64 bit)
- os/kernel: 5.15.89-1-MANJARO (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.19.4
- go/linking: dynamic
- go/tags: none

Are you on the latest version of rclone? You can validate by checking the version listed here: Rclone downloads

--> Yes, 1.61.1

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


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

rclone lsd Mega:

The rclone config contents with secrets removed.

type = mega
user = MY EMAIL
pass = REMOVED
Well, any help would be greatly appreciated. Thanks in advance.

A log from the command with the -vv flag

Unfortunately I was not able to find the logs.

Thanks in advance for any help.

P.S.: due to the above, I think I'll not be able to copy files from my local system to Mega.

hello and welcome to the forum,

please post the full output of rclone lsd Mega: -vv, ok to redact dir/filenames.

Thank you very much for your answer.

Below is the full output:

rclone lsd Mega: -vv
<7>DEBUG : rclone: Version "v1.61.1" starting with parameters ["rclone" "lsd" "Mega:" "-vv"]
<7>DEBUG : rclone: systemd logging support activated
<7>DEBUG : Creating backend with remote "Mega:"
<7>DEBUG : Using config file from "/home/ewsg/.config/rclone/rclone.conf"
Failed to create file system for "Mega:": couldn't login: Object (typically, node or user) not found

did you follow all these steps, what was the result?

So, I've followed some of them. Well, but is MegaCMD a requirement to use rclone with Mega?

I am asking because I had many problems with that CLI tool in the past.

Also, I get to make login at Mega using rclone, so I think that no poblem regarding the password is happening.

please follow all the steps, as per documentation and post all the results.
else going to be hard to troubleshoot

no. tho some create a webdav server using megacmd and have rclone use that webdav to copy files to mega.

sorry, not understanding what you mean.
as per the debug log, rclone couldn't login:
from the docs
"consider changing your password temporarily to pure alphanumeric characters, in case that helps."

1 Like

Hi again,

Many, many thanks. :slight_smile:

And sorry for bothering you.

It's working now. It seems the problem was relly in the password I was using at Mega (full of special characters, etc, etc...hahaha).

Well, at least for now I could run rclone ls Mega_Rclone: and rclone lsd Mega_Rclone: -vv without any issues.

But, I think that the ouputs from the commands are being returned after a bit of a delay. Is this normal?


good to know that the documentation advice is spot-on.

not surprised.
i would use a rclone debug log and look at the timestamps, to see where the slow down is from.

Great. Thank you very much. I'll do that.

Thanks for your help and kidnness.

thanks for the thank

Hello again,

Just a last question, please: does rclone works by default on "some kind" of incremental mode?

yes, but can you explain in more detail what you mean?

Oh, I just wanted to make sure that every day (I'll automate everything via cron) only new and changed files will be copied.

Also, I am trying to set the log level but --log-level INFO, for example, does not works. What am I doing wrong, please?

correct, rclone copy

post the exact command


Here it goes:

rclone --log-level INFO
  1. there is no command, such as sync/copy/move
  2. there is no source
  3. there is no dest

and should test using --dry-run

Great. It worked. :wink:

1 Like

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