# Something bad happened again **URL:** \ **Category:** Bug Reports\ **Created:** [May 26, 2026, 2:59pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314 "2026-05-26T14:59:12Z")\ **Posts on this page:** 14\ **Page:** 2
**Author:** ![Adrian\_L](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/adrian_l/32/2810_2.png) [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)\ **Post date:** [June 8, 2026, 2:09am UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/23 "2026-06-08T02:09:03Z")
Hi @edharris Since the root user password seems to be working. The next step is to ensure that the root user has remote access privileges. You can copy the SQL command from another thread to do this. > [@DK0066 - \[error\] Error - DK0066: IMPORT\_DB\_DUMP: Error (1): YERROR 1130 (HY000): Host 'XXXXX' is not allowed to connect to this MariaDB server](https://community.kinsta.com/t/dk0066-error-error-dk0066-import-db-dump-error-1-yerror-1130-hy000-host-xxxxx-is-not-allowed-to-connect-to-this-mariadb-server/5830): > > Dear all, this one drove me nuts for a bit so writing this here for everyone, but especially for me slight_smile I was getting the DK0066 error like many experienced. 1- First issue was a normal site creation in DevKinsta. I fixed this by following this thread: [Something bad happened: in create new site - #17 by StormChild](https://community.kinsta.com/t/something-bad-happened-in-create-new-site/2190/17) 2- I then faced a similar issue when importing a site from Kinsta. I was getting an error and when looking into the main.log file I saw the error [error] Error - DK0066… Let us know how it goes. 🙂 ---
**Author:** ![edharris](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/edharris/32/5603_2.png) [@edharris](https://community.kinsta.com/u/edharris)\ **Post date:** [June 8, 2026, 2:42pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/24 "2026-06-08T14:42:21Z")
None of those instructions are working for me, and now when I try to go back and replicate the previous step in my last message, I’m getting the access denied message again. I’m sorry I’m not super familiar with the terminal, docker, etc, but I’m doing my best to follow along with the instructions. I’d love to be able to use DevKinsta for local development integrated with my Kinsta account (the same way I used to with WP Engine and Local) but having to work through this level of troubleshooting to get it working is really challenging. Is there a plan to roll out an update to DevKinsta that fixes this issue? It seems to have been reported in various forms for 3+ years now. ---
**Author:** ![Phease69](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Phease69](https://community.kinsta.com/u/Phease69)\ **Post date:** [June 8, 2026, 2:50pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/25 "2026-06-08T14:50:09Z")
I completely agree, I am coming from the same workflow in WPE. I have followed all steps meticulously again today, including these new ones, and got to the final steps where it asked to grant privileges in the SQL and I got: ERROR 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: YES) ERROR 1227 (42000): Access denied; you need (at least one of) the RELOAD privilege(s) for this operation MariaDB [(none)]\> ---
**Author:** ![Phease69](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Phease69](https://community.kinsta.com/u/Phease69)\ **Post date:** [June 8, 2026, 2:51pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/26 "2026-06-08T14:51:11Z")
Hi Adrian, I am still trying with this one. And followed these steps, got access to the DB then came to do the privileges but and got: ERROR 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: YES) ERROR 1227 (42000): Access denied; you need (at least one of) the RELOAD privilege(s) for this operation MariaDB [(none)]\> ---
**Author:** ![Adrian\_L](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/adrian_l/32/2810_2.png) [@Adrian\_L](https://community.kinsta.com/u/Adrian_L)\ **Post date:** [June 8, 2026, 11:33pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/28 "2026-06-08T23:33:30Z")
@Phease69 @edharris At this stage, it may be simpler to completely uninstall both DevKinsta and Docker Desktop and start from scratch. **Please note that this is only recommended if you are prepared to lose any existing WordPress data from your current DevKinsta app.** To uninstall both DevKinsta and Docker Desktop, please do the following: 1. Delete all existing DevKinsta **Containers** , **Images** , and **Volume** within the Docker Desktop. (You may need to stop the container first if they are running before Docker Desktop will allow you to delete the container) ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/3/37a558acb4027e0bce733b82eabf8b239636b18c.png) 1. Uninstall both the DevKinsta app and Docker Desktop. 2. After the Apps have been uninstalled, **make sure that these folders are deleted.** ```auto /Users//Library/Application Support/DevKinsta /Users//Library/Logs/DevKinsta ``` 1. Reinstall DevKinsta and Docker Desktop. If the problem still persists, please share with us again the latest DevKinsta main.log file located at: `/Users//Library/Logs/DevKinsta` ---
**Author:** ![Phease69](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Phease69](https://community.kinsta.com/u/Phease69)\ **Post date:** [June 9, 2026, 9:22am UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/29 "2026-06-09T09:22:44Z")
it will be the third time I have done this, but OK, lets give it another go. I’ll come back to you with the log file. ---
**Author:** ![Phease69](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Phease69](https://community.kinsta.com/u/Phease69)\ **Post date:** [June 9, 2026, 12:00pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/30 "2026-06-09T12:00:02Z")
Hi Adrian, log file sent. ---
**Author:** ![VladimirM](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/vladimirm/32/2786_2.png) [@VladimirM](https://community.kinsta.com/u/VladimirM)\ **Post date:** [June 9, 2026, 2:07pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/32 "2026-06-09T14:07:33Z")
Hello @Phease69 👋 I’m sorry to hear this still persists. I do notice that the error has code 1044, instead of 1045 we usually see but it’s the same output - the access is denied to superadmin user for some reason. Please test a different solution posted [here](https://community.kinsta.com/t/something-bad-happened-in-create-new-site/2190/23). 1. Stop and remove the DB container: `docker rm -f devkinsta_db` 2. Remove the DB volume: `docker volume rm devkinsta_db_data` 3. Recreate the DB container using the password shown in `docker inspect`: ```auto docker run -d --name devkinsta_db \ --network devkinsta_network \ -e MARIADB_ROOT_PASSWORD= \ -v devkinsta_db_data:/var/lib/mysql \ kinsta/devkinsta_db:1.3.6 ``` 1. Verify authentication works: `docker exec -it devkinsta_db mysql -uroot -p -e "SELECT 1;"` ---
**Author:** ![Phease69](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Phease69](https://community.kinsta.com/u/Phease69)\ **Post date:** [June 9, 2026, 3:34pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/33 "2026-06-09T15:34:17Z")
> [@VladimirM](#): > > ```auto > docker run -d --name devkinsta_db \ > --network devkinsta_network \ > -e MARIADB_ROOT_PASSWORD= \ > -v devkinsta_db_data:/var/lib/mysql \ > kinsta/devkinsta_db:1.3.6 > > ``` I get this… “zsh: no such file or directory: password” ---
**Author:** ![Phease69](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Phease69](https://community.kinsta.com/u/Phease69)\ **Post date:** [June 9, 2026, 3:44pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/34 "2026-06-09T15:44:41Z")
Ah wait, I realised I copied the commands in full and there is a password bit. Sorry, I am not a terminal user, so this stuff might as well be in Chinese for all I understand it! Just trying to muddle through. Ironically the reason I want to use DevKinsta is to avoid all this stuff! But I think it might have worked. I am testing now. ---
**Author:** ![Phease69](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Phease69](https://community.kinsta.com/u/Phease69)\ **Post date:** [June 9, 2026, 3:48pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/35 "2026-06-09T15:48:51Z")
Hmmm, sadly Vladimir, it does not work still. I did get two steps closer…it now breaks at step 3. ![Screenshot 2026-06-09 at 16.47.18](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/f/f88e268ec3c39df5d4805bac179fa714ada31663.png) ---
**Author:** ![Phease69](https://avatars.discourse-cdn.com/v4/letter/p/5f9b8f/32.png) [@Phease69](https://community.kinsta.com/u/Phease69)\ **Post date:** [June 9, 2026, 4:12pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/36 "2026-06-09T16:12:48Z")
This seems to be the error now, and happens when I try to import a site from Kinsta: **[2026-06-09 16:45:07.154] [error] [ipcMainStep] Error in operation SITE\_CREATION, step rsync: Error: Encountered an error in child process 16273: 23. rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1861) [generator=3.2.7]** ![Screenshot 2026-06-09 at 16.47.18](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/f/f88e268ec3c39df5d4805bac179fa714ada31663.png) It starts to download the files, gets to almost complete, then fires this error. I can confirm though, that I can now create blank new sites, which I couldn’t do before, so that bit seems to be working. We just now need to fix the ability to pull sites from the Kinsta host . ---
**Author:** ![jackirish](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/jackirish/32/1361_2.png) [@jackirish](https://community.kinsta.com/u/jackirish)\ **Post date:** [June 9, 2026, 10:01pm UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/37 "2026-06-09T22:01:48Z")
Hi @Phease69 ! 👋 Can you please DM the name of the site in question to myself, @Adrian_L , @merineth, and @VladimirM so we can check the site on MyKinsta? The error in question: `some files/attrs were not transferred` usually indicates a permissions issue or a broken symlink on the original site. ---
**Author:** ![ShawnC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/shawnc/32/880_2.png) [@ShawnC](https://community.kinsta.com/u/ShawnC)\ **Post date:** [June 14, 2026, 12:57am UTC](https://community.kinsta.com/t/something-bad-happened-again/6314/41 "2026-06-14T00:57:38Z")
Howdy @Phease69 👋 , Thanks for hanging in there and sharing as you go friend. I took a look at the main.log file you shared, as well as the staging site you indicated failed the pull. Just to rule out permissions, I reset the file permissions for that staging environment. When you have a chance, may you try the following steps, but first a warning: **⚠ WARNING:** _Following the steps below will delete the databases for any other local sites you currently have running in DevKinsta. If you have other local sites you need to keep, you must export their databases via Adminer first._ Now, the steps: 1. Close **DevKinsta**. 2. Open **Docker Desktop**. 3. On the left-hand sidebar, click on **Volumes**. 4. Find the volume named `devkinsta_db_data` and delete it. 5. Restart **DevKinsta**. The rationale here is that when checking the main.log. DevKinsta gets all the way to the database step of creating your site “owenreed” and then this happens (lines 2046–2047): ```auto Command 'mysql -u root -p ****** -e "create database Owen_Reed;"' on devkinsta_db finished with exit code 1 [ipcMainStep] Error in operation SITE_CREATION, step database: Error (1): ERROR 1044 (42000) at line 1: Access denied for user 'root'@'localhost' to database 'Owen_Reed' ``` In other words, root can log in but has lost its `CREATE`/global privileges. That points to a corrupted or incomplete grant table inside the DB container’s data volume, usually from an unclean shutdown, a Docker Desktop update mid-run, or a half-finished password reset. When DevKinsta boots up, it _ **should** _ notice the missing volume, recreate the `devkinsta_db` container with the correct root permissions, and you should be able to pull or create your “Owen Reed” site successfully. Once you’ve given this a try, please let us know how it goes. [Previous page](https://community.kinsta.com/t/something-bad-happened-again/6314.md?page=1)