Q: Date/Time this occurred (Provide your time zone also)
A: 04/08/2026
Q: DevKinsta Version
A: 2.13.6 (2.13.6.9096)
Q: OS Version
A: Tahoe 26.4
Q: Docker Desktop Version
A: 4.68.0
Q: Were any error codes or messages observed? If so, what were they?
A: '“something bad happened” and DK0066
Q: Detailed Description of the Problem
A: The Kinsta team has been aware of this sequence of errors for years but it has never been patched. The app is intended to provide an easy way to import a remote site onto local environment, but this has never been possible for some of us. This sequence is probably familiar to some users.
- DevKinsta starts up and starts the Docker containers
- You select site import, choose intended environment
- Import begins, but immediately fails to create a DB
You discover the problem is that DevKinsta doesn’t actually configure the devkinsta_db container correctly; it fails to set the password to the one generated by DevKinsta. Instead, the password is empty, so the solution is extremely simple:
mariadb -u root -p
ALTER USER ‘root’@‘localhost’ IDENTIFIED BY ‘pw-from-DevKinsta’;
This fixes the issue and the process continues. After waiting patiently for the entire site to be downloaded, you are then hit with DK0066. You get the host IP from the log and once again run straight-forward commands to fix the issue.
GRANT ALL PRIVILEGES ON *.* TO ‘root’@‘ip-from-DevKinsta-log-file’ IDENTIFIED BY ‘pw-from-DevKinsta’ WITH GRANT OPTION;
FLUSH PRIVILEGES;
While this seems to work, this restarts the entire download process.
Can anyone explain why exactly this happens and has been consistently happening for a long time? The solutions may be simple but that is no excuse to not have an official fix. Users should not have to manually set DB password and grant privileges to specific IP every time. Do y’all know exactly what causes this? It seems like an issue with one app attempting to configure another app and the OS prevents DevKinsta from doing all the things it is supposed to do in Docker.
