Unable to login to mega

Help and Support
1

What is the problem you are having with rclone?

I am unable to login to mega

I got

Failed to create file system for "Mega:/credit-sales": couldn't login: Try again

What is your rclone version (output from rclone version)

rclone v1.57.0

  • os/version: debian 11.2 (64 bit)
  • os/kernel: 5.10.0-10-amd64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.17.2
  • go/linking: static
  • go/tags: none

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

Mega (Pro, paid)

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

 rclone ls Mega:/ -vvvvvvvvvvvvvvvvvvvvvvv  --dump bodies

The rclone config contents with secrets removed.


[Mega]
type = mega
user = user@redacted.com
pass = pasW....redatcted... P55Dew
hard_delete = true

A log from the command with the -vv flag

2

hi,
not sure what the issue is, but to cut down the length of the debug log, can add
--retries=1 --low-level-retries=1

how did you create the remote, using rclone config or text editor?

have you done any testing using megacmd?

is ths the first time using rclone + mega?

3

Thanks for reply

I created the config file using rclone config.

Here the dump with new options


2022/02/21 10:31:21 DEBUG : rclone: Version "v1.57.0" starting with parameters ["rclone" "ls" "Mega:/project" "-vvvvvvvvvvvvvvvvvvvvvvv" "--dump" "bodies" "--retries=1" "--low-level-retries=1"]
2022/02/21 10:31:21 DEBUG : Creating backend with remote "Mega:/project"
2022/02/21 10:31:21 DEBUG : Using config file from "/home/user/.config/rclone/rclone.conf"
2022/02/21 10:31:21 DEBUG : You have specified to dump information. Please be noted that the Accept-Encoding as shown may not be correct in the request and the response may not show Content-Encoding if the go standard libraries auto gzip encoding was in effect. In this case the body of the request will be gunzipped before showing it.
2022/02/21 10:31:21 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2022/02/21 10:31:21 DEBUG : HTTP REQUEST (req 0xc000778000)
2022/02/21 10:31:21 DEBUG : POST /cs?id=1559537306 HTTP/1.1
Host: g.api.mega.co.nz
User-Agent: rclone/v1.57.0
Content-Length: 49
Content-Type: application/json
Accept-Encoding: gzip
[{"a":"us0","user":"user@project.com"}]
2022/02/21 10:31:21 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2022/02/21 10:31:21 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2022/02/21 10:31:21 DEBUG : HTTP RESPONSE (req 0xc000778000)
2022/02/21 10:31:21 DEBUG : HTTP/1.1 200 OK
Content-Length: 59
Access-Control-Allow-Headers: Content-Type, MEGA-Chrome-Antileak
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: Original-Content-Length
Access-Control-Max-Age: 86400
Cache-Control: no-store
Connection: keep-alive
Content-Type: application/json
Original-Content-Length: 59
[{"s":"0GL_2VMmF5Yd1OGnjv52cfuoq7ryOa1HCOwwqO5Wh-8","v":2}]
2022/02/21 10:31:21 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2022/02/21 10:31:21 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2022/02/21 10:31:21 DEBUG : HTTP REQUEST (req 0xc000778100)
2022/02/21 10:31:21 DEBUG : POST /cs?id=1559537307 HTTP/1.1
Host: g.api.mega.co.nz
User-Agent: rclone/v1.57.0
Content-Length: 109
Content-Type: application/json
Accept-Encoding: gzip
[{"a":"us","user":"user@project.com","uh":"yg0xV9MD7y91988hJKBQcA","sek":"nZtcR5PSc8V7docxNq_HLw"}]
2022/02/21 10:31:21 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2022/02/21 10:31:21 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2022/02/21 10:31:21 DEBUG : HTTP RESPONSE (req 0xc000778100)
2022/02/21 10:31:21 DEBUG : HTTP/1.1 200 OK
Content-Length: 2
Access-Control-Allow-Headers: Content-Type, MEGA-Chrome-Antileak
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: Original-Content-Length
Access-Control-Max-Age: 86400
Cache-Control: no-store
Connection: keep-alive
Content-Type: application/json
Original-Content-Length: 2
-3
2022/02/21 10:31:21 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2022/02/21 10:31:21 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2022/02/21 10:31:21 DEBUG : HTTP REQUEST (req 0xc000546300)
2022/02/21 10:31:21 DEBUG : POST /cs?id=1559537307 HTTP/1.1
Host: g.api.mega.co.nz
User-Agent: rclone/v1.57.0
Content-Length: 109
Content-Type: application/json
Accept-Encoding: gzip
[{"a":"us","user":"user@project.com","uh":"yg0xV9MD7y91988hJKBQcA","sek":"nZtcR5PSc8V7docxNq_HLw"}]
2022/02/21 10:31:21 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2022/02/21 10:31:21 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2022/02/21 10:31:21 DEBUG : HTTP RESPONSE (req 0xc000546300)
2022/02/21 10:31:21 DEBUG : HTTP/1.1 200 OK
Content-Length: 2
Access-Control-Allow-Headers: Content-Type, MEGA-Chrome-Antileak
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: Original-Content-Length
Access-Control-Max-Age: 86400
Cache-Control: no-store
Connection: keep-alive
Content-Type: application/json
Original-Content-Length: 2
-3
2022/02/21 10:31:21 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2022/02/21 10:31:21 Failed to create file system for "Mega:/project": couldn't login: Try again
4

The problem is still here. At today, is 10 days since last backup copied from local to mega online.

We are looking for an alternative, but I really LOVE rclone. And cannot diagnose and debug without an help.

Is there any kind of paid assistance about rclone?

5

I don't know why, but people seem to have problems like this with rclone and mega every now and again :frowning:

You can try using rclone with mega-cmd. You set up mega-cmd to export a webdav server and use rclone with that. It works quite well - see mega: option to use `mega-cmd` internally to access storage · Issue #3660 · rclone/rclone · GitHub .

6

Also check out this bit in the rclone docs which is specifically about failure to login.

7

I see this in the doc

Rclone does not currently close mega sessions (you can see them in the web interface), however closing the sessions does not solve the issue.

Today, we logged in into Mega and closed all sessions.
It works again.

Is there a 'close mega session' in somewhere?

8

Damn. 15m after, same problem... damn

9

Are you running rclone lots of times? Every time you run the rclone binary it has to log in and collect all the object info. I think that is what Mega objects to.

Can you run an rclone mount or rclone rcd to send commands to? Mega prefers either of those.

10

one workaround is to use megacmd, start its webdav server.
then create a webdav remote pointing to that webdav server

11

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