Mega remote couldn't login error

Help and Support
1

What is the problem you are having with rclone?

Mega remote nonstop saying couldn't login now for three days....earlier it did worked however but not now.

What is your rclone version (output from rclone version)

Latest Rclone 1.55.0

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Windows 10 (Also tried on Google Colab same error)

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)

Tried all commands below:

rclone lsf Mega:foldername -vv --dirs-only

rclone lsd Mega:foldername -vv

rclone lsf Mega:foldername -vv --dirs-only --mega-debug

The rclone config contents with secrets removed.

[Mega]
type = mega
user = users@website (none of the letters is capital here)
pass = encrypted text (only small and capital letter with some numbers no special symbols/characters)

A log from the command with the -vv flag

rclone lsf Mega:folder -vv --dirs-only --mega-debug
2021/04/11 15:39:18 DEBUG : Using config file from "C:\\path\\.config\\rclone\\rclone.conf"
2021/04/11 15:39:18 DEBUG : rclone: Version "v1.55.0" starting with parameters ["rclone" "lsf" "Mega:folder" "-vv" "--dirs-only" "--mega-debug"]
2021/04/11 15:39:18 DEBUG : Creating backend with remote "Mega:folder"
2021/04/11 15:39:18 DEBUG : Mega: detected overridden config - adding "{v6fxV}" suffix to name
2021/04/11 15:39:20 DEBUG : *go-mega*: Retry API request 1/10: Try again
2021/04/11 15:39:20 DEBUG : *go-mega*: Retry API request 2/10: Try again
2021/04/11 15:39:20 DEBUG : *go-mega*: Retry API request 3/10: Try again
2021/04/11 15:39:20 DEBUG : *go-mega*: Retry API request 4/10: Try again
2021/04/11 15:39:20 DEBUG : *go-mega*: Retry API request 5/10: Try again
2021/04/11 15:39:21 DEBUG : *go-mega*: Retry API request 6/10: Try again
2021/04/11 15:39:21 DEBUG : *go-mega*: Retry API request 7/10: Try again
2021/04/11 15:39:22 DEBUG : *go-mega*: Retry API request 8/10: Try again
2021/04/11 15:39:24 DEBUG : *go-mega*: Retry API request 9/10: Try again
2021/04/11 15:39:26 DEBUG : *go-mega*: Retry API request 10/10: Try again
2021/04/11 15:39:32 Failed to create file system for "Mega:folder": couldn't login: Try again
2

hello and welcome to the forum,

do you think it could be related to the new vesion v1.55.0?

try

  • login to the website, look for the logs or notfications.
  • re-create a new remote.
3

I doubt it could be new version since same account worked 2 times earlier with new version only

Already tried new remote creation with new password too

Update:Tried with 1.54.1 and new remote...same error alas!

4

did you log into the website and look around for issues?

5

It might be that your account has been locked out for a while. Mega seems to do that.

6

Hmm locked out as specifically on rclone? Because I am still able to use it via website and app.

If rclone specific should I keep trying everyday to find out how long lockdown or just let it rest for 7days or so

7

Try once per day should be ok.

The other thing you could try is megacmd.

8

Well so far still doing same but this time new line on Retry 1/10:

Creating backend with remote "MegaHH:"
2021/04/16 06:55:35 DEBUG : MegaHH: detected overridden config - adding "{v6fxV}" suffix to name
2021/04/16 07:00:37 DEBUG : *go-mega*: Retry API request 1/10: Post "https://g.api.mega.co.nz/cs?id=2953100390&sid=P_1wbt5BK30DA7ob2Vq-TUJhQ2w2bjJLYkYwRzANys5T4Gw1qYXtofwo3Q": net/http: timeout awaiting response headers
2021/04/16 07:00:38 DEBUG : *go-mega*: Retry API request 2/10: Try again
2021/04/16 07:00:38 DEBUG : *go-mega*: Retry API request 3/10: Try again
2021/04/16 07:00:38 DEBUG : *go-mega*: Retry API request 4/10: Try again
2021/04/16 07:00:38 DEBUG : *go-mega*: Retry API request 5/10: Try again
2021/04/16 07:00:39 DEBUG : *go-mega*: Retry API request 6/10: Try again
2021/04/16 07:00:39 DEBUG : *go-mega*: Retry API request 7/10: Try again
2021/04/16 07:00:40 DEBUG : *go-mega*: Retry API request 8/10: Try again
2021/04/16 07:00:42 DEBUG : *go-mega*: Retry API request 9/10: Try again
2021/04/16 07:00:44 DEBUG : *go-mega*: Retry API request 10/10: Try again
2021/04/16 07:00:50 Failed to create file system for "MegaHH:": couldn't login: Try again

PS:could it be too many files and hence rclone don't like mega account or so because it business account and there is shit ton of files in it shared by many...hopefully not else rip my ways to transfer my data server side using colab

9

The other thing you can do is set up the megacmd tools - they have a webdav server which rclone can talk to.

Mega don't document their API so sometimes we come across things we don't know how to solve like this :frowning:

10

Seems like a success with megacmd webdav...works like normal remote so pretty easy as well.
Thx for the help :smiley:

11

i guess i spoke too quick...works like a charm on rclone on desktop but when went into google colab starts giving me error like below:

2021/04/16 22:55:11 DEBUG : rclone: Version "v1.55.0" starting with parameters ["rclone" "lsf" "mrzix:" "--dirs-only" "-vv"]
2021/04/16 22:55:11 DEBUG : Creating backend with remote "mrzix:"
2021/04/16 22:55:11 DEBUG : pacer: low level retry 1/10 (error Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused)
2021/04/16 22:55:11 DEBUG : pacer: Rate limited, increasing sleep to 20ms
2021/04/16 22:55:11 DEBUG : pacer: low level retry 2/10 (error Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused)
2021/04/16 22:55:11 DEBUG : pacer: Rate limited, increasing sleep to 40ms
2021/04/16 22:55:11 DEBUG : pacer: low level retry 3/10 (error Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused)
2021/04/16 22:55:11 DEBUG : pacer: Rate limited, increasing sleep to 80ms
2021/04/16 22:55:11 DEBUG : pacer: low level retry 4/10 (error Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused)
2021/04/16 22:55:11 DEBUG : pacer: Rate limited, increasing sleep to 160ms
2021/04/16 22:55:12 DEBUG : pacer: low level retry 5/10 (error Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused)
2021/04/16 22:55:12 DEBUG : pacer: Rate limited, increasing sleep to 320ms
2021/04/16 22:55:12 DEBUG : pacer: low level retry 6/10 (error Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused)
2021/04/16 22:55:12 DEBUG : pacer: Rate limited, increasing sleep to 640ms
2021/04/16 22:55:12 DEBUG : pacer: low level retry 7/10 (error Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused)
2021/04/16 22:55:12 DEBUG : pacer: Rate limited, increasing sleep to 1.28s
2021/04/16 22:55:13 DEBUG : pacer: low level retry 8/10 (error Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused)
2021/04/16 22:55:13 DEBUG : pacer: Rate limited, increasing sleep to 2s
2021/04/16 22:55:14 DEBUG : pacer: low level retry 9/10 (error Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused)
2021/04/16 22:55:16 DEBUG : pacer: low level retry 10/10 (error Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused)
2021/04/16 22:55:16 ERROR : : error listing: couldn't list files: Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused
2021/04/16 22:55:16 DEBUG : 3 go routines active
2021/04/16 22:55:16 Failed to lsf with 2 errors: last error was: error in ListJSON: couldn't list files: Propfind "http://127.0.0.1:4443/path/": dial tcp 127.0.0.1:4443: connect: connection refused

Got any ideas whats going wrong on colab?

12

Did you run a megacmd server on google colab also? You will need to, or find some way of tunneling the connections back to your server.

13

Webdav didnt worked despite running on colab itself but using get command of megacmd helps the case with colab transfers...cheers again :sweat_smile:

1 Like
14

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