DK0066: IMPORT_DB_DUMP: Error (1): (ERROR at line 1: Unknown command '\-'

I have attempted to delete all containers and images and a full reset. I know just get “errors”.

You may try the solution from @BocaJuniors through the link below. I tried the same solution on my end and it worked.

I think this has worked!

1 Like

@LeeKIJO Great to know that this has worked for you.

If ever you have further questions or encountered some issues, please let us know.

Hi all,

I’ve tried all the solutions above, but nothing helps. I also read that the latest DevKinsta update should fix this issue, but that’s not the case for me.

ANy other fixes available? I’m not able to pull sites now.

Hi @jarno! Thank you for your reply!

I’m sorry to hear that this issue is persisting for you. We are happy to help further investigate into this matter with you.

I would like to review the latest main.log file of your DevKinsta installation to see more details about the current issue occurring. If you could please direct/private message me this file that will assist us in the investigation.

The path of the main.log file does vary depending on if you are running DevKinsta on Windows or Mac. Below, you may find a link to our help article that provides the path to this file for both platforms:

We look forward to hearing from you!

Best regards

Thank you for sending me the log, @jarno!

After reviewing the main.log file I am seeing several errors mentioning a JSON syntax error is occurring. We are investigating into this further with our team and we will update you as soon as possible once we have more details to share.

We do appreciate your patience while we investigate into this matter further.

If you do have any questions in the meantime please don’t hesitate to reply.

Best regards

I’m having a lot of performance problems with Kinsta. It’s impossible to use WPML’s automatic translation tool properly, for example! Support told me to do it locally with Devkinsta …

But I’m getting this error that prevents me from doing it locally!

I’m losing days and days of development, and it’s getting very frustrating.

Here are the logs:

Do you have a solution please?

Hi @Diamir! Thank you for your reply.

I’m sorry to hear that you are experiencing this difficulty with importing your site into DevKinsta. I understand that this can be a frustrating situation. I assure you however we are here and happy to help look into what solutions are possible.

To help us get started could you please confirm the following information?

DevKinsta version

Operating system version

Docker version

Having this information will assist us in our investigation.

We look forward to hearing from you!

Hi Andrew, do you have an update? I’m still not able to pull this site from Kinsta.

Hi @jarno can you send me via private message the latest DevKinsta main.log and the domain name of the Kinsta site you’re trying to pull to the DevKinsta app? Thanks!

Hi @jarno,

Thank you for sharing the main.log file. I reviewed it and found that the Kinsta site import to the Devkinsta app is failing at the MySQL import step due to this problematic line in the SQL file.

/*!999999\- enable the sandbox mode */

This issue is supposed to be resolved in the latest version of Devkinsta (2.13.4).

Could you please confirm whether you are using the latest version of the Devkinsta app? Thanks!

Hi there,

I can confirm that this is NOT fixed in DevKinsta 2.13.4. The only workaround is to manually remove that line from the backup.sql file on the server during the import.

Hello Jarno :wave:

Sorry to hear this, we will try to replicate this and forward the information to our developers for further review.

Kind regards

Hello again @jarno :wave:

Apologies for the delayed response.

I’ve tested this on both Mac (OS Sonoma 14.3) and Win10. I made sure that the site, or rather it’s SQL dump, contains the line /*M!999999- enable the sandbox mode */ (the M was there when I tested an export on your site, I didn’t add it).

I was able to pull the site from Kinsta to DevKinsta successfully on both Mac and Win machine.

Can you please tell me the exact operating system, docker version and DevKinsta version (you stated you are using the latest version) you are using?

Kind regards

I can confirm that the issue is not fixed. It’s shocking that I opened this thread in the end of May, and now is November and still not able to clone a website using DevKinsta :exploding_head:

backup.sql file still includes /*!999999\- enable the sandbox mode */ at the top of the file.

Also, there is no DevKinsta log file at /Users/<yourusername>/Library/Logs/DevKinsta (as it mentioned in docs)

  • Docker Desktop 4.5.0
  • DevKinsta 2.13.4
  • macOS Sequoia

Hi @taras, I am sorry to hear that you are still facing this issue. However, we still couldn’t replicate this issue with this machine:

I have the following default settings set in the Docker Desktop.

If the issue continues after you’ve checked the Docker Desktop settings, it may be best to completely uninstall and then reinstall both DevKinsta and Docker Desktop. Before uninstalling the applications, please create a backup of your local sites to avoid losing any data.

Please let us know how it goes.

@Adrian_L I fully agree with @taras. I just purchased a new MacBook Pro, with a fresh installation of Docker Desktop and DevKinsta.

I was able to pull a site that doesn’t contain that line in the .sql dump successfully, but I get the same error on the specific site that does contain that line.

I also checked my Docker Desktop settings, and set them to the same settings as in the screenshot.

I’m still not able to pull this site.

Hello @jarno and @taras :wave:

I’m sorry that this issue still persists. I have noticed that when I export the database it does have the line /*!999999\- enable the sandbox mode */ However, after I import it to my test site and then export the db again on my test site, the line is edited automatically with M being added after /* - it turns too /*M!999999\- enable the sandbox mode */ which is probably why I don’t get the error when trying to pull the site from Kinsta.

I believe that the issue exists on your end, but it is not due to the bug in the app itself. It is somehow specific to those sites for some reason, which we haven’t been able to determine.

If you are experiencing this on the live site:

  • make a staging (or refresh the existing staging so it would be an exact copy of the live site).
  • If the issue persists, log in via SSH, export the db with wp db export, then use the wp db clean command and lastly use wp db import filename.sql (where filename is the actual filename of the exported database)
  • Once that is done, try pulling the site again from Kinsta.

I understand that this is frustrating, especially since we repeated a few times that the bug was fixed. We absolutely acknowledge that you are still experiencing this issue, however, the bug is definitely fixed, this seems to happen only with specific sites.

As such I wanted to address that DevKinsta is a free product, currently only in Maintenance Mode, which means that developers are only working on security updates and bugs. We are not able to fix site-specific issues due to that, but we try to help any way we can. Please try the above workaround and let me know if that works.

Hi @VladimirM - I followed the steps, but unfortunately I get the same error when pulling the staging environment after running wp db export - wp db clean - wp db import.