From cff85f0b9551881be535a4847b56742451e6b476 Mon Sep 17 00:00:00 2001 From: Nick Craig-Wood Date: Thu, 16 May 2019 10:10:58 +0100 Subject: [PATCH] docs: add note on failure to login to mega docs --- docs/content/mega.md | 45 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) diff --git a/docs/content/mega.md b/docs/content/mega.md index cd04dc379..4bbb5e17b 100644 --- a/docs/content/mega.md +++ b/docs/content/mega.md @@ -99,6 +99,51 @@ messages in the log about duplicates. Use `rclone dedupe` to fix duplicated files. +### Failure to log-in ### + +Mega remotes seem to get blocked (reject logins) under "heavy use". +We haven't worked out the exact blocking rules but it seems to be +related to fast paced, sucessive rclone commands. + +For example, executing this command 90 times in a row `rclone link +remote:file` will cause the remote to become "blocked". This is not an +abnormal situation, for example if you wish to get the public links of +a directory with hundred of files... After more or less a week, the +remote will remote accept rclone logins normally again. + +(If you have lots of commands to run one after the other a better way +of doing this might be to run `rclone rcd` and then use `rclone rc` to +run the commands over the API. This will avoid logging in each time.) + +Rclone does not currently close mega sessions (you can see them in the +web interface), however closing the sessions does not solve the issue. + +If you space rclone commands by 3 seconds it will avoid blocking the +remote. We haven't identified the exact blocking rules, so perhaps one +could execute the command 80 times without waiting and avoid blocking +by waiting 3 seconds, then continuing... + +Note that this has been observed by trial and error and might not be +set in stone. + +Other tools seem not to produce this blocking effect, as they use a +different working approach (state-based, using sessionIDs instead of +log-in) which isn't compatible with the current stateless rclone +approach. + +Note that once blocked, the use of other tools (such as megacmd) is +not a sure workaround: following megacmd login times have been +observed in sucession for blocked remote: 7 minutes, 20 min, 30min, 30 +min, 30min. Web access looks unaffected though. + +Investigation is continuing in relation to workarounds based on +timeouts, pacers, retrials and tpslimits - if you discover something +relevant, please post on the forum. + +So, if rclone was working nicely and suddenly you are unable to log-in +and you are sure the user and the password are correct, likely you +have got the remote blocked for a while. + ### Standard Options