ERROR: Uploaded file size and local file size don’t match

  • Resolved nextstep

    (@nextstep99)


    5 years, 5 months ago

    ERROR: Uploaded file size and local file size don’t match.

    Having just gone on the BackWPup forum with a dropbox API connection issues, where apparently the fault was with my web hosting.

    Coincidentally I am now receiving this error: ERROR: Uploaded file size and local file size don’t match.

    The techsupport at Lifetime.hosting have looked into it, and again, like the API issue insist it is a problem with the plugin or dropbox. Note: The api issue apparantly was magically fixed as I did ask for an explanation to post on that forum entry to close it off with a solution, but they don’t know why or won’t give me one.

    Before contacting Lifetime.Hosting support about the error message, I did some research courtesy Professori Google .

    I came up with some findings and in particular I pointed them to this post (and specific reply) but they insist there is no problem at their end.

    “this problem usually happens when BackWPUp uploading backup file to Dropbox, and during this process, a network problem happens and Dropbox returns error file size not correct. Please try again to see if it’s work!”
    Full post here:
    https://www.ads-software.com/support/topic/error-uploaded-file-size-and-local-file-size-dont-match-6/

    The support at Lifetime.Hosting have responded:

    With this: We can’ give you the much support on this issue you can contact dropbox support and if they suggest any changes need to be done from the server side we will do it for you.
    And this: Since this a plugin related case, you need to contact their support for further assistance regarding the error. We don’t have any expertise with this plugin or its errors.

    Before the google search I did “the usual” when there is a wordpress plugin not performing properly. So far I have gone into wordpress and tried the following:
    ~ Disabled all plugins except backwpup
    ~ Activated twenty seventeen theme
    ~ I also created a new backwpup job from scratch. (Including the api connection)

    The problem still occurs.

    I have three other webhosts with addon domains and there is no problem with any of them. Or any of the addon sites that I have there.

    It is only happening on Lifetime.Hosting. I have 3 addon domain sites with them and they are all having the same problem. To me there is a common issue and that is the problem is with Lifetime.Hosting.

    If you can give some sort of assistance or advice that would be appreciated, as the tech support at Lifetime.Hosting are incapable.

    Here is the debug file from the request on the post above (less any private info “please give me your server information ( BackWPUp-> Settings -> Infomation tab -> press Get Debug Info )”

    Many thanks in advance for any assistance you can offer.

    WordPress version: 5.2.2
    BackWPup version: 3.6.9
    PHP version: 7.0.33 (64bit)
    MySQL version: 5.7.26-cll-lve
    cURL version: 7.65.0
    cURL SSL version: OpenSSL/1.0.2r
    WP-Cron url: https://******/wp-cron.php
    Server self connect: Response Test O.K.
    Document root: /home2/******/public_html/addons/******
    Temp folder: /home2/******/public_html/addons/******/wp-content/uploads/backwpup-******-temp/
    Log folder: /home2/******/public_html/addons/******/wp-content/uploads/backwpup-******-logs/
    Server: LiteSpeed
    Operating System: Linux
    PHP SAPI: litespeed
    Current PHP user: ******
    Maximum execution time: 180 seconds
    BackWPup maximum script execution time: 30 seconds
    Alternative WP Cron: Off
    Disabled WP Cron: Off
    CHMOD Dir: 0755
    Server Time: 10:29
    Blog Time: 10:29
    Blog Timezone: UTC
    Blog Time offset: 0 hours
    Blog language: en-US
    MySQL Client encoding: utf8
    PHP Memory limit: 512M
    WP memory limit: 40M
    WP maximum memory limit: 512M
    Memory in use: 52.00 MB
    Loaded PHP Extensions:: Core, PDO, Phar, Reflection, SPL, SimpleXML, bcmath, calendar, ctype, curl, date, dom, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imap, intl, ionCube Loader, json, libxml, litespeed, mbstring, mcrypt, mysqli, mysqlnd, openssl, pcre, pdo_mysql, pdo_sqlite, posix, session, sockets, sqlite3, standard, timezonedb, tokenizer, wddx, xml, xmlreader, xmlwriter, xsl, zip, zlib

    • This topic was modified 5 years, 5 months ago by nextstep. Reason: redact site ID info
    • This topic was modified 5 years, 5 months ago by nextstep.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support happyAnt

    (@duongcuong96)

    Hi @nextstep99
    please try add these following lines to .htaccess file

    # BEGIN litespeed noabort
<IfModule rewrite_module>
RewriteEngine On
RewriteRule .* - [E=noabort:1]
</IfModule>
# END litespeed noabort

    After that, try again, hope that helps ??

    Thread Starter nextstep

    (@nextstep99)

    Unfortunately no ??

    I tried in a few different positions, before and after wordpress, and some of the other plugin entries. … should it go anywhere in particular?

    Plugin Support happyAnt

    (@duongcuong96)

    Hi @nextstep99
    Please replace class-destination-dropbox-api.php located in backwpup/inc/ with the one here:
    https://www.dropbox.com/s/b16c67m6mps4siy/class-destination-dropbox-api.php?dl=0
    is that help?
    Thank you!

    Thread Starter nextstep

    (@nextstep99)

    Thank you! but sadly, no joy. ??

    Thread Starter nextstep

    (@nextstep99)

    Hi duongcuong, I woke up this morning to find that I was no longer getting the BackWPup error message emails and all is working properly again. I don’t know whether Lifetime.hosting did ‘something’ or not, their responses are terse and uninformative. I have heard nothing back from them, and they have closed off the help request.

    I will mark this as closed and resolved, however I can’t tell you why. Apologies.

    I have given a review including a 5 star rating.

    Many thanks for all your assistance.

    • This reply was modified 5 years, 5 months ago by nextstep. Reason: typo
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘ERROR: Uploaded file size and local file size don’t match’ is closed to new replies.