Could not delete site config file DK0072

DevKinsta Application Support
1

When adding my first site from an existing environment on Kinsta I received the notice “Something bad happened” at 16% and couldn’t continue.

I followed some instructions from this forum post Something bad happened on 16% of importing site

I deleted the recommended container and volume in Docker. no fix

Then, I did a Clean / Purge all data, however, I forgot to cancel the site creation and close DevKinsta before doing this. Now the site is stuck at 33% with the error “Could not delete site config file DK0072.”

Tried adding a new site again (same site) and now both are stuck with the same message.

2

Hi @blackmatter,

Welcome to the Kinsta Community forums! Thank you for reaching out!

I am sorry to hear you are experiencing these issues while you attempt to create a site in DevKinsta. I understand the importance of finding a solution to these issues so you can get to working on your site as soon as possible!

I see that you are trying to import one site from MyKinsta. I also see you attempted to create a new site again using that same environment but both are appearing stuck with the DK0072 error.

It does seem like a related issue could be occurring between both sites. However, to confirm the exact issue we would like to review the main.log file generated by DevKinsta. This log file contains additional debug log information. As this file can contain sensitive information if you could please send a direct message to me with the main.log file attached it is appreciated.

Below you may find a link to our help article that goes into details about where to locate the main.log file:

If you could also confirm the following information that will help us in our investigation:

Date/Time this occurred (Provide your time zone also)

DevKinsta Version

OS Version

Docker Desktop Version

We look forward to hearing back from you!

5

Hi @blackmatter!

Thank you for DMing me the main.log file and environment information.

I have reviewed the main.log file and noticed some unusual errors. I do see it appears after the initial DevKinsta related containers were created, during the site creation attempt there was an error creating the database for the site. It appears that DevKinsta was unable to connect using the root user and the access was denied. This indicates that something may have prevented the root password from being synced/set correctly.

I also see that later in the log DevKinsta began having issues finding the DevKinsta related containers in Docker. This indicates that the DevKinsta related Docker containers were not running as expected.

As this is your first attempt at creating a site in DevKinsta it might be best to try and recreate all of the DevKinsta related Docker containers as well as the volumes.

To accomplish this, please stop DevKinsta by first closing it’s window, and then in the top bar secondary click it’s icon and choose to stop and shutdown DevKinsta. This should fully stop all of DevKinsta’s containers. This will ensure all containers/volumes can be properly deleted in Docker Desktop.

This next step will now delete all files/folders, containers and volume information related to DevKinsta including local site data. As I understand however you currently do not have any working sites in DevKinsta.

Next, open Finder and delete the DevKinsta folder under your home folder, as well as the DevKinsta folder located at Library (accessible by opening Go from the top menu, and then holding the option key) >> Application Support >> DevKinsta.

Next, open Docker Desktop and delete all of the DevKinsta related containers. Then, still in Docker Desktop switch over to the volumes and delete/erase all DevKinsta related volumes. This should effectively clear out all data and fully ensure all DevKinsta related containers/volumes have been removed.

After this step I would also recommend fully quitting Docker Desktop and relaunching it.

Once we are at this clean slate state please launch DevKinsta again. This will cause all of the DevKinsta related Docker containers to be downloaded, and recreated. This will also recreate the DevKinsta volumes and files. This process should also fully sync up the database passwords and any other configurations.

Once this process has completed and DevKinsta is running, please create a new local WordPress site in DevKinsta itself. This is to test if the site creation process for a new site can complete successfully. If this process is successful, than please try importing your site again from MyKinsta to see if that too can now complete successfully.

If you do have any questions about these steps, or need further assistance please let us know. We are standing by and ready to help!

Can't install or import a site: "Something bad happened"
6

Thank you. I went through that process and was able to reset everything.

I attempted to add a site from Kinsta and immediately got an error.

image
image1060×650 33.2 KB

I also have this notice about disk space.

“Docker disk space is almost full. Your Docker disk space is dropped below 2 GB. Running out of disk space causes data loss. > See what to do”

Could this be the reason for the error?

I clicked the link “See what to do” and can’t figure out what the actual issue is. It seems like there is enough space but I don’t know enough about this to troubleshoot.

7

Hi @blackmatter,

In response to the “Disk Usage almost full” warning, please follow these steps:

  1. Open Docker Desktop and go to Settings.
  2. Navigate to the Resources section and increase the Disk Usage limit to a higher value.
  3. After adjusting the settings, close both DevKinsta and Docker Desktop.
  4. Relaunch the application.

image
image902×656 63.3 KB

If the issue persists, kindly send us the latest main.log file so we can investigate further. Thank you!

8

Thanks, this was already at the max (1.82 TB). The issue still persists. I included the latest main.log file.

(main.log redacted)

10

Thank you for sharing the main.log file. I review it and it appears that this specific error is what causing the “Something bad happened” failure when creating/pull sites through DevKinsta.

[2026-02-12 08:27:02.637] [error] [ipcMainStep] Error in operation SITE_CREATION, step database: Error: Error (1): UERROR 1045 (28000): Access deni     ed for user 'root'@'localhost' (using password: YES)
1704     at /Applications/DevKinsta.app/Contents/Resources/app.asar/main.prod.js:2:837383
1705     at tryCatch (/Applications/DevKinsta.app/Contents/Resources/app.asar/main.prod.js:8:1843893)
1706     at Generator.<anonymous> (/Applications/DevKinsta.app/Contents/Resources/app.asar/main.prod.js:8:1845538)
1707     at Generator.next (/Applications/DevKinsta.app/Contents/Resources/app.asar/main.prod.js:8:1844442)
1708     at asyncGeneratorStep (/Applications/DevKinsta.app/Contents/Resources/app.asar/main.prod.js:8:1836779)
1709     at _next (/Applications/DevKinsta.app/Contents/Resources/app.asar/main.prod.js:8:1836999)
1710     at processTicksAndRejections (node:internal/process/task_queues:95:5)

You can try the steps provided here to try to resolve this error.

11

That was able to stop the error on the pryority bank site.

It didn’t appear to be working so I went through Part Two – GRANTING PRIVILEGES TO ‘root’ USER. I was not able to enter a password in terminal. When I got to that stage, it wouldn’t recognize keystrokes.

I also did Part three and updated the password in the config.json file.

NEXT: I went back to devkinsta and tried adding a new site from my kinsta account. BG Aero. This hit the same “something bad happened” warning at 16% too. I followed the steps again, but this time it didn’t correct the error.

NEXT: I went back to the pryority bank site. Selected Sync. Then selected “pull from kinsta”. I selected the pryority bank site and it started copying files to my local drive. It got stuck at 50%.

“Failed to import database dump DK0066”

12

Hi Paul,

Thanks for the update and sorry you’re running into another error.

This message means DevKinsta couldn’t import your local site’s database backup into the database on your MyKinsta site, so the push/import didn’t complete successfully.

Could you please send us a new copy of your main.log file from DevKinsta? That will help us see exactly what caused the import to fail and what to fix next.

Hopefully, after this. Everything will go through.

13

Thanks for the help. here is the most recent main.log file.

(main.log redacted)

14

@blackmatter

Thank you for sharing the main.log file. I checked it, and this seems to be the specific error causing the pull action to fail.

[2026-02-20 08:44:57.994] [error] Error - DK0066: IMPORT_DB_DUMP: Error (1): YERROR 1130 (HY000): Host '172.172.0.4' is not allowed to connect to this MariaDB server

Can you please check and you’re showing this warnings in the Docker Desktop, if you do, please proceed to repair or re-apply the configuration as shown in the screenshot.

image
image1148×598 80.6 KB

image
image1338×276 52.8 KB

Please also try creating a fresh WordPress site in DevKinsta to see if the issue persists.

Lastly, please also try requesting a downloadable backup on the Kinsta site you’re trying to pull, then manually import the backup using the Create site >> Import from backup option in DevKinsta.

Let us know how it goes.

16

There are no errors in Docker like your screen shot. Everything appears to be fine.

I created a New WordPress site: Immediate error at 20% (something bad happened)

I created a Custom WordPress site and uploaded the backup of Pryority Bank: immediate error at 28% (something bad happened).

(main.log redacted)

18

Hello @blackmatter :waving_hand:

We are still seeing database ‘root’ user error in the logs, which means that the main issue with the ‘root’ user hasn’t been resolved.

I think you need to redo this entire process. I know it can be frustrating (I myself had to do it a couple of times when I had the issue): Error: Something bad happened - when trying to import site from myKinsta - #15 by VladimirM

I noticed you stated that ‘I was not able to enter a password in terminal. When I got to that stage, it wouldn’t recognize keystrokes.’

This is normal. It is often a security feature for password to not be shown when being entered. So please retry the steps :folded_hands:

19

I’ve run through the steps in that article 5 times and it never works.

In PART ONE, when I get to step 6, I run these commands one by one and it returns:
/bin/sh: 2: USE: not found
/bin/sh: 3: FLUSH: not found
/bin/sh: 4: ALTER: not found
/bin/sh: 5: FLUSH: not found

In PART TWO, after step 2 I add the password and it returns:
ERROR 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: YES)

Step 3 returns:
bash: GRANT: command not found

I’ve also completed PART 3 and have confirmed that password I’m using is the one set in ‘Services’ config.json.

I need this to work. I’ve wasted too much time on trying to fix this and it’s impacting my business. At this point, can/should I just remove everything and start over?

20

@blackmatter

I believe the best approach at this point is to just delete all DevKinsta containers, images, and volumes in Docker Desktop. After that, uninstall both DevKinsta and Docker Desktop. Next, delete the DevKinsta folder under your home folder, as well as the DevKinsta folder located at Library (accessible by opening Go from the top menu, and then holding the option key) >> Application Support >> DevKinsta. Then reinstall DevKinsta to start fresh.

(Please note that deleting the DevKinsta volumes from the Docker Desktop will remove any existing custom site data for any local site that exists in DevKinsta)