Cannot login to Mega

Help and Support
1

STOP and READ USE THIS TEMPLATE NO EXCEPTIONS - By not using this, you waste your time, our time and really hate puppies. Please remove these two lines and that will confirm you have read them.

What is the problem you are having with rclone?

I am unable to login to Mega with rclone. I am able to login in a browser just fine, but I cannot with rclone. I've tried recreating the config, verified the commands, verified my username and password, and turned off 2fa. Still the issue remains.

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

rclone v1.75.0

  • os/version: Microsoft Windows 11 Pro 25H2 25H2 (64 bit)
  • os/kernel: 10.0.26200.9168 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.26.5
  • go/linking: static
  • go/tags: cmount

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

Mega

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

'''rclone sync N:\Documents mega:/Documents --fast-list --progress --size-only'''

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

'''
[mega]
type = mega
user = XXX
pass = XXX
'''

A log from the command that you were trying to run with the -vv flag

'''
2026/08/25 16:00:16 DEBUG : rclone: Version "v1.75.0" starting with parameters ["c:\\progra~1\\rclone\\rclone" "sync" "n:\\Documents" "mega:/Documents" "--fast-list" "--progress" "--size-only" "-vv"]
2026/08/25 16:00:16 DEBUG : Creating backend with remote "n:\\Documents"
2026/08/25 16:00:16 DEBUG : Using config file from "C:\\Users\\REDACTED\\AppData\\Roaming\\rclone\\rclone.conf"
2026/08/25 16:00:16 DEBUG : fs cache: renaming cache item "mega://Documents" to be canonical "//?/n:/Documents"
2026/08/25 16:00:16 DEBUG : Creating backend with remote "n:\\Documents"
2026/08/25 16:00:16 DEBUG : mega root 'ISOs': Using username and password to initialize the Mega API
2026/08/25 16:00:27 CRITICAL: Failed to create file system for "mega://Documents": couldn't login: unexpected end of JSON input
'''

I'm not sure what's wrong. Everything was working fine earlier today. Any suggestions?

2

as a test, now, i created a mega remote and it is working fine.

rclone config redacted mega01:
[mega]
type = mega
user = XXX
pass = XXX
2fa = XXX
session_id = XXX
master_key = XXX

rclone lsd mega: -vv
2026/08/25 19:18:55 DEBUG : rclone: Version "v1.75.0" starting with parameters ["rclone" "lsd" "mega:" "-vv"]
2026/08/25 19:18:55 DEBUG : Creating backend with remote "mega:"
2026/08/25 19:18:55 DEBUG : Using config file from "c:\\data\\rclone\\rclone.conf"
2026/08/25 19:18:55 DEBUG : mega root '': Using previously stored session ID and master key to initialize the Mega API
          -1 2026-08-25 19:15:42        -1 zork

can you post the output of rclone lsd mega: -vv

3

C:\Program Files\rclone>rclone lsd mega: -vv
2026/08/25 16:41:54 DEBUG : rclone: Version "v1.75.0" starting with parameters ["rclone" "lsd" "mega:" "-vv"]
2026/08/25 16:41:54 DEBUG : Creating backend with remote "mega:"
2026/08/25 16:41:54 DEBUG : Using config file from "C:\Users\n8chavez\AppData\Roaming\rclone\rclone.conf"
2026/08/25 16:41:54 DEBUG : mega root '': Using username and password to initialize the Mega API
2026/08/25 16:42:04 CRITICAL: Failed to create file system for "mega:": couldn't login: unexpected end of JSON input

That's odd that my rclone config redacted contained a lot less information than yours. Mine had no session_id or master_key

4

how did you create the remote?

  1. using rclone config
    or
  2. edit the rclone.conf text file
5

Both. I even deleted the file, and used rclone config to recreate the entire file. Nothing worked.

6

use rclone config

7

I did. I said I used both.

8

yes, i understand that. just making clear, must use rclone config

9

have you create other remotes before or is this your first time?
have you ever created a mega remote before or is this your first time?

let's start over
use rclone config, to create a new remote named mega2

10

I've created about 10-12 remotes before, using rclone for everything from Nextcloud, Pcloud, google drive, mounting mega (before 2fa), to webdav on a VPS. Mega has always been the most temperamental.

I created another mega remote, mega2. I used different sync paths from my script, in case they were the problem. They were not.

C:\Program Files\rclone>rclone config redacted
[mega]
type = mega
user = XXX
pass = XXX

[mega2]
type = mega
user = XXX
pass = XXX

Here's the command from the bat script I always run, and the result.

C:\Program Files\rclone>c:\progra~1\rclone\rclone sync e:\ISOs mega2:/ISOs --fast-list --progress --size-only -v
2026/08/25 17:26:16 CRITICAL: Failed to create file system for "mega2:/ISOs": couldn't login: unexpected end of JSON input

Again, I noticed your rclone redacted has more information that mine. Should I be concerned with that?

11

no point in using rclone sync until rclone about remote: and rclone lsd remote: work
and use -vv not -v

yes.
maybe try rclone config -vv and create mega3

12

The result was the same:

[mega3]
type = mega
user = XXX
pass = XXX

13

Perhaps it is having an issue with my password? It's a randomly generated long password, with special characters. I'm not sure why there's an issue now, when it worked earlier in the day, but I'll try changing it.

Edit - That didn't work. Nothing changed.

14

Ok. I solved it. Short version, it was my firewall blocking rclone. Longer version, that doesn't make me seem like an idiot, updating to Windows 11 25H2 26200.9168 reverted my "Private" mode connections to "Public" without saying anything. So my firewall rules, which were set to allow only "Private" mode connections were blocking rclone.

Just an FYI, in case that happens to you. Thanks.