New to the community? Start here

[Shipper Pro] AJAX Unable to extract sqls dump sql from archive

Hi,

I’ve just tried to migrate a website using Shipper Pro.

I tried first to migrate using the API, it says that it should take a little less than 2 hours. But after a moment I get disconnected from the website, and when I login again I see the migration stopped.

So I decided to go with Package Migration, as suggested by Shipper in the first place.

Package was created successfully, but when I tried to import it in the new website it failed with this log:

We encountered an error!

Please check the log below

[2021-06-16 15:28:23] - Analyzing paths: [1] of [2]: 50%
[2021-06-16 15:28:25] - Analyzing paths: [2] of [3]: 66%
[2021-06-16 15:28:26] - Analyzing paths: [3] of [4]: 75%
[2021-06-16 15:28:27] - Analyzing paths: [4] of [5]: 80%
[2021-06-16 15:28:28] - Analyzing paths: [5] of [6]: 83%
[2021-06-16 15:28:29] - Analysis done, [5200] files total
[2021-06-16 15:28:30] - Stowing config file [/home/XXX.fr/public_html/shipper-working/files/wp-includes/.htaccess]
[2021-06-16 15:28:30] - Deployed 1424 files of 5200 total
[2021-06-16 15:28:31] - Deployed 2291 files of 5200 total
[2021-06-16 15:28:32] - Deployed 3480 files of 5200 total
[2021-06-16 15:28:34] - Deployed 4400 files of 5200 total
[2021-06-16 15:28:35] - Deployed 5047 files of 5200 total
[2021-06-16 15:28:36] - Deployed 5200 files of 5200 total
[2021-06-16 15:28:52] - Dumped SQL file is not found. Trying once again.
[2021-06-16 15:28:52] - AJAX: Unable to extract [sqls/dump.sql] from archive [/home/XXX.fr/public_html/202106161319-YYY.shipper.zip]

Any idea?
Thanks!

Wed, 16 Jun 2021 13:39:39
More Shipper Pro discussions
Shipper Pro
  • Kris Tomczyk
    • Ex Staff

    Hi Arom77

    I hope you are doing good today.

    Could you follow the below guide to send site and FTP access so that we could create a new Package and test this in our lab? I checked our system and so far there was only 1 report with this error.

    ========================

    Please don’t share any sensitive information (i.e credentials) in the Support Forum.

    Please send it through our secure contact form here https://premium.wpmudev.org/contact/#i-have-a-different-question and make sure that subject is “I have a different question” and:

    – Mark to my attention: ATTN: Kris

    – Site access:
    — login URL
    — username
    — password

    – FTP credentials
    — host
    — username
    — password
    — port

    – Link back to this thread

    Please confirm here in the thread that you have sent that message.

    Kind Regards,
    Kris

  • Arom77
    • Froggy

    Hi Kris

    Problem solved I’m pretty sure: the server quota was almost full. Is this something that Shipper Pro pre-check could check and warn the user about?

    So I increased it and migrated using the API method.

    It worked without any problem except one: the migration (apparently?) stopped because I used the Mask Login Area feature of Defender Pro. Maybe something to improve here?

    As a result I deactivated Mask Login Area on both source and destination websites and the API migration went through and succeded :)

    Best Regards

  • Nebu John
    • FLS

    Hi Arom77 ,

    Glad to know that API migration helped with migrating the site.

    Usually, if Shipper finds any potential issues with your package during the Pre-flight Check, it will notify you before proceeding with the package build.

    [attachments are only viewable by logged-in members]

    stopped because I used the Mask Login Area feature of Defender Pro

    I checked this on a test site but wasn’t able to replicate the issue. The API migration works well with Masked Login Area enabled at both ends. Do you have the logs of the failed migration, if yes, can you please share them with us so that we can take a closer look?

    Kind Regards,
    Nebu John