MegaCloud: ban resolved and a couple of questions about rclone.conf

Help and Support
1

Over a month ago, I asked for help with a permanent MEGAcloud ban affecting rclone due to hidden, bulk, and unwanted uploads of 15-20 GB of folders and index files, mostly generated by the Synology NAS (hidden @eadir folders), unknowingly uploaded to MEGAcloud.

I asked MEGA support several times for help, but they proved incapable of handling this situation, even at the second level.

Forced to give up on rclone, I gave it up and started using the inadequate MEGAcmd.

Today, April 9th, I noticed that MEGAcloud removed the ban—I don't know how long ago—and rclone started working with my credentials.

I'm wondering if, in these cases of bans, saving and then using rclone.conf can restore normal rclone functionality on MEGAcloud. I'd also like to know how to numerically limit file uploads per unit of time, and how to set values ​​for parallel uploads.

In other words, I'd like to know how to set a low limit to avoid a second ban, and an intermediate limit to proceed safely without taking forever and going full throttle...

2

Hi,

Did some research for you. Here are my results.

You should be able to choose one of these methods and avoid getting the ban again.

Research suggests that it was your IP address that was banned so a VPN might have overcome that immediately.

Rclone mega info controlling tranfers.

1 Like
3

Tanks

understand that using a VPN (which I do have), the OP's question remains: can using the rClone configuration file "rclone.conf" restore normal rclone functionality on MEGAcloud?
Thanks

An AI provided me with instructions on how to numerically limit file uploads per unit of time and how to set the values ​​for parallel uploads, so I no longer need them.

4

Not 100% sure what you mean regarding rcline.conf.

That file should have your mega S4 settings in it and there are no Flags to put in so as long as you can connect it to s4 those settings don't change.

Just do an rclone lsd s4remote:bucket

5

Just to be precise: rclone.conf instead of rcline.conf

Regarding this, and only regarding the Cloud Mega API and not the S4 buquet, Antrophic's Cloud AI informed me that in the event of a ban - provided you haven't changed the login settings -restoring a previously saved copy of rclone.conf also restores a connection banned by IP.
We know AIs talk a lot of bullshit (1*), and this could be another one.
Besides, I haven't had the chance to test it. So I'm reporting it just for the record.
(1*) And in fact, Cloud itself caused a second, hopefully temporary, ban for too many connections by recommending the --fast-list parameter, which, according to the article you linked, is to be avoided!

6

If it would make you feel more comfortable you can run

Rclone config

D for delete

Choose your maga remote

Then go in and create a new one.

Rclone.conf I would doubt has anything related to your IP address. It's just your endpoint and access ID and Secret key.

I doubt that anything in the configuration file is a carryover from being banned.