Importing issues

Is there a way to bypass the ‘destroy everything’ nature of cancelling an import.

I have large and complex sites that simply cannot be imported from Kinsta. I have developed scripts that help me sync all the data and the database which work great.
However one of the issues I have run into is the strange nature of the cancelling of the import. It attempts to restore everything from the previous state, when in fact, I just want it to stop what it is doing.

And upon setting up a new site, where the import always fails, if I try to cancel the import, it deletes everything, which is unhelpful.

Hi @Aporia

I understand your concerns, and I appreciate your feedback. I will submit it as a feature request because, unfortunately, that’s how the Cancel action currently functions. Thank you for bringing this to our attention.

As for the failed import, we can take a closer look at why it is failing. In order to better assist you, can you please provide the following information:

OS Version:
DevKinsta Version:
Docker Desktop Version:

Please also send me DevKinsta’s main.log file via private message. You can get the main.log file by clicking on “Reveal log file in File Manager” under the Help and Support page in DevKinsta.

Also, does creating a site with a fresh WordPress install within DevKinsta also fail?

Best,

I am running the latest DevKinsta and Docker on MacOS

Thank you for sharing the main.log file. I checked the site you are trying to pull but didn’t notice any obvious issues that would cause the pull action to fail. The entries in the main.log file also do not provide a clear explanation for the import failure.

Could you please create a new, fresh WordPress site in DevKinsta using the “Add Site” >> “New WordPress Site” option? Let me know if this also fails or if it completes successfully. This will help us determine whether the issue is related to your site data or with the DevKinsta app itself.

Also, if you see any of these warnings in the Docker Desktop, please click on the “Re-apply configuration” Repair" as another application might conflict with the DevKinsta app.

Let us know how it goes.

No docker issues and I can successfully create a new wordpress.
The issue is the sync. It has always been the sync. I have large sites with large databases.

Hello there :wave:

Have you ever tried to get a downloadable backup of the site and import it via DevKinsta? If that fails, it could mean that it’s something specific to the site or the database.

The main.log sadly doesn’t really give us much to go on, so please test what I suggested above and let me know what’s the outcome.

Kind regards

I can do that, but if I cannot use sync, DevKinsta is not very helpful as a development environment.

I have gone through this complaint before. The lack of error messages suggests that the sync function is not atomic enough to help debug this issue.

Hello there :wave:

I understand what you’re saying, however, what I’m aiming at is trying a few things for troubleshooting purposes. It might help us figure out where the issue is. Changing the sync function is something we can ask our developers to do, but given that DevKinsta is in maintenance & security development mode, I don’t believe that change would be happening anytime soon.

You can try with downloadable backup and/or try syncing just the database and maybe try syncing one table only. It could be that you have a large database table, or even a row that’s too big to process causing the process to fail.

At this moment, I can only guess, but please let me know once you try Downloadable backup, if it works, and whether you can sync only one table at a time (test with a smaller one). If those actions fail, please re-share your main.log.

Kind regards