rclone / rclone/rclone

Support for MEGA with 2FA in Docker environment (stable, non-blocking performance)

Open
#9,277 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
59.9k
Forks
5.4k
Avg merge
2d 14h
Merged PRs (30d)
48

Description

What problem are you trying to solve?

I am using rclone with MEGA cloud storage in a Docker environment.
Currently, using MEGA with 2FA (two-factor authentication) is difficult or not well supported, especially in automated/containerized setups.

Additionally, under load (multiple transfers, background services like media servers), performance can become unstable or cause delays.

Proposed solution
  • Add full support for MEGA accounts with 2FA in rclone (including non-interactive / headless login support).
  • Provide a secure way to authenticate using tokens or session reuse that works well inside Docker containers.
  • Improve stability and performance when running rclone in Docker (no blocking, no lag under load).
  • Optional: environment variable support for authentication (for Docker usage).
Alternatives considered
  • Using manual login or disabling 2FA (not secure, not acceptable).
  • Using external scripts to refresh sessions (unstable and complex).
Additional context

Use case:

  • Docker-based homelab (NAS, media stack, backups)
  • Continuous sync with MEGA
  • Need for stable, secure, and automated operation

It would be very helpful if rclone could better support modern security (2FA) while remaining efficient in containerized environments.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named in the issue, so begin by locating rclone's MEGA backend and authentication handling. The requested outcome would need headless 2FA support, secure token or session reuse in Docker, and stable non-blocking performance under load.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
authentication, cloud, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.