• Resolved alexzaragoza21

    (@alexzaragoza21)


    Hello updraft plus team, first of all I want to say thank you for having this kind of plugin, no other backup plugin can be compared to this one. However, I need your help, I was totally done with the installation and authentication of updraft in my website when suddenly a message appear on top of my admin dashboard, it says:

    “Success: you have authenticated your Dropbox account (though part of the returned information was not as expected – your mileage may vary)
    Dropbox error: Error in call to API function “users/get_current_account”: request body: could not decode input as JSON (400)”

    What does it mean? how can I solve this. I check my dropbox and It seems that the back ups are there, but not pretty sure If those will work well because of that message I have. Hope you can help me. Thank you so much in advance.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor bcrodua

    (@bcrodua)

    Hi,

    What version of the plugin is currently installed?

    Please could you send us a copy of the latest backup log? This can be found in the Existing Backups tab.

    The contents will be too long to post here directly, but you can use an online service such as Pastebin or Dropbox, and post the link here.

    Best Wishes,
    Bryle

    Thread Starter alexzaragoza21

    (@alexzaragoza21)

    I am using the latest version, 1.14.7

    https://www.dropbox.com/s/bvpnoqn745lzv8d/log.fe7d58ee6f97.txt?dl=0

    that’s the link of the log file @bcrodua. Hope you can Instruct me to do something to solve this issue. Thank you very much. I pray for the continuous success of the plugin.

    Plugin Author David Anderson / Team Updraft

    (@davidanderson)

    The backup log looks fine – i.e. successful backup.

    The error itself means that when it was looking up your account info to display info on the account, there was a problem. But the actual sending of backups to the account is not having a problem.

    David

    Sorry to answer in this post but I have the same problem on one of my websites. I thought maybe my extra info is of use for this problem.

    I’m using the Updraft plugin version 2.14.7.0 with WP 4.7.9 (I want to make a backup before I upgrade WP to the latest version).

    What have I done already;
    1. Tried to work with the free and UpdraftPlus versions of the plugin.
    2. Tried to wipe the settings before trying again.
    3. Deactivated all other plugins to see if that helped, but it didn’t.

    I noticed that it seems like the orange ‘Complete setup’ screen to authenticate the site shows up twice instead of once. Maybe that’s the problem?

    My install doesn’t make a backup either. Here’s the content of the latest log file:

    0000.000 (0) Opened log file at time: Tue, 15 May 2018 13:08:06 +0000 on https://www.domain.nl
    0000.001 (0) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 2.14.7.0 WP: 4.7.9 PHP: 5.6.35 (fpm-fcgi, Linux srv2a.digihosting.nl 2.6.32-042stab128.2 #1 SMP Thu Mar 22 10:58:36 MSK 2018 x86_64) MySQL: 5.6.27 WPLANG: nl_NL Server: Apache/2.4.33 (Unix) OpenSSL/1.0.1e-fips safe_mode: 0 max_execution_time: 900 memory_limit: 256M (used: 24.4M | 25.3M) multisite: N openssl: OpenSSL 1.0.1e-fips 11 Feb 2013 mcrypt: Y LANG:  ZipArchive::addFile: Y
    0000.002 (0) Free space on disk containing Updraft's temporary directory: 336136.8 MB
    0000.004 (0) Tasks: Backup files: 1 (schedule: unset) Backup DB: 1 (schedule: unset)
    0000.005 (0) Semaphore (fd, wp_options) being initialised
    0000.020 (0) Requesting semaphore lock (fd) (apparently not via scheduler)
    0000.021 (0) Semaphore lock (fd, wp_options) failed (line 43)
    0000.022 (0) Failed to gain semaphore lock (fd) - another backup of this type is apparently already active - aborting (if this is wrong - i.e. if the other backup crashed without removing the lock, then another can be started after 3 minutes)

    Hope you have any clues on what could be the problem. Thanks in advance!

    Plugin Author David Anderson / Team Updraft

    (@davidanderson)

    marjons, that error log does not resemble the problem in this thread at all. Please do open your own topic so that it can be looked at.

    Sorry about that David, it seemed like the same problem.

    Gladly, my problem solved itself when I exported and re-imported the database, so there’s no need for my own topic anymore.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Error in call to API function “users/get_current_account”: request body..’ is closed to new replies.