Duplicati: Mega.nz as Backend - ResourceNotExists

Created on 29 Apr 2020  路  5Comments  路  Source: duplicati/duplicati



  • [x] I have searched open and closed issues for duplicates.

Environment info


  • Duplicati version: 2.0.5.1-1
  • Operating system: Ubuntu 19.10
  • Backend: Mega.nz

Description


Can't use my new mega account to backup. Whenever I try to verify the connection it returns:
"Failed to connect: API response: ResourceNotExists"
I also tried to continue but the backup won't run further than "Checking Backend Details". Same error then.
I used a new Mega Account without 2FA!

EDIT:
I was using the wrong password, maybe just add a more detailed version of the API response, if available.

Steps to reproduce

  1. Setup Backup
  2. Use Mega.nz as Backend
  3. Enter details
  4. Click "Verify Connection"
  5. Wait for the error


  • Actual result:
    Fails because of "ResourceNotExists"
  • Expected result:
    Connection should be successful or fail during invalid credentials

Screenshots



grafik
grafik

Debug log


All 5 comments

@Bungeefan Previously I've used duplicity and it couldn't connect to an account that has been created via Mega web interface(it creates some new type of account). Only account created via api worked. That account works with duplicati.

  1. Delete your account
  2. Install megatools
  3. Create account
    megareg --name=Your Name [email protected] --password=YourPa$$w0rD --register

It should help.

@devops-caspian Thanks anyway.
Is that a workaround or the way to go?

@Bungeefan Forget what I've previously said. I've just created a new account at mega.nz via web interface and used duplicati 2.0.5.1-1 installed on Ubuntu 19.10. It works.

@devops-caspian then tell me what I am doing wrong. Did you set something specific in the MEGA account settings? And what did you enter as Username in duplicati? Is it wrong when I am using the email?

Omg I am just dumb... @devops-caspian sry for your time.
I used the wrong password on the new account. Now it is working for me.
Maybe parse the API response better and show the user a detailed version of the error, if available.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ethauvin picture ethauvin  路  5Comments

dudelson picture dudelson  路  5Comments

thomasyi17 picture thomasyi17  路  3Comments

zappe picture zappe  路  5Comments

mnaiman picture mnaiman  路  6Comments