Howdy @criana
Welcome to the Kinsta Community!
I’m sorry to hear that you’re experiencing issues with our DevKinsta app. To help us investigate the problem further, could you please send me a private message with the DevKinsta main.log file?
For Mac users, you can typically find the log file at the following location:
/Users/<yourusername>/Library/Logs/DevKinsta/main.log.
Thank you!
Gladly, just sent over the log file in a private message.
Alright @criana,
Thank you kindly for your patience friend.
This was an odd one, but this could be a /.quarantine directory inside the /public directory.
Looking over the main.log, right before the progress indicator returns a failure, there’s a failed: Permission denied message.
It looks like the /.quarantine directory may contain suspected malware.
May you try removing that directory from the environment you’re pulling into DevKinsta, then try again, and let me know if the operation is successful.
@ShawnC I just logged into SFTP for both the Live and Dev environments, found the .quarantine folder, and checked for files; there were none. But to make matters more interesting, I also can not delete it. I got a permissions denied when trying to remove it. I tried SSH as well with no luck. Screenshot attached.
Hi @criana,
Thank you for your response. I checked both the Live and Dev environments and can no longer find the .quarantine folder. It appears that it may have been successfully removed already.
However, I see this error in the log as well:
[2026-05-30 12:22:37.039] [error] SyntaxError: Unexpected non-whitespace character after JSON at position 1608
Can you please double check wp-config.php and confirm that DOMAIN_CURRENT_SITE isn’t set to undefined or wrong domain?
Could you please try the following as well:
devkinsta_We will wait for your update.
This is what worked for me on Windows:
TL;DR
Once you’ve gotten your error from trying to import your site, copy the DB password shown in the site info.
Then do this:
docker exec devkinsta_db mysql -u root -e “ALTER USER ‘root’@‘localhost’ IDENTIFIED BY ‘PASTE_PWD’; FLUSH PRIVILEGES;”
docker exec devkinsta_db mysql -u root -pPASTE_PWD -e “CREATE USER IF NOT EXISTS ‘root’@‘%’ IDENTIFIED BY ‘PASTE_PWD’; GRANT ALL PRIVILEGES ON . TO ‘root’@‘%’ WITH GRANT OPTION; FLUSH PRIVILEGES;”
Should be g2g.
Long version:
The MariaDB container comes up on a volume that already has data, so it skips password initialization even though DevKinsta hands it a MYSQL_ROOT_PASSWORD. That leaves the DB’s root account with a password (or none) that doesn’t match the one in DevKinsta’s config, so every create database over localhost fails with 1045, and the later import over the Docker network fails with 1130 because there’s no root@'%' grant for the FPM container’s subnet (172.172.0.x). When Docker Desktop restarts, it cleared the containers but persistent Docker volumes seemed to have remained. The MariaDB container reuses the old volume data and skips password initialization, even though the MYSQL_ROOT_PASSWORD environment variable is set, which causes a mismatch between DevKinsta’s expected password and the actual database state.
Confirm your DB password in the import info within DevKinsta,
Then, with the containers running (don’t run DevKinsta as admin), open Command Prompt and run these two commands, substituting your exact password for PASTE_PWD:
docker exec devkinsta_db mysql -u root -e "ALTER USER 'root'@'localhost' IDENTIFIED BY 'PASTE_PWD'; FLUSH PRIVILEGES;"
docker exec devkinsta_db mysql -u root -pPASTE_PWD -e "CREATE USER IF NOT EXISTS 'root'@'%' IDENTIFIED BY 'PASTE_PWD'; GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' WITH GRANT OPTION; FLUSH PRIVILEGES;"
The first command sets root@localhost to the password DevKinsta expects (fixing the 1045 on database creation). The second creates root@'%' and grants it (fixing the 1130 when the FPM container connects over the network). Note there’s no space after -p. Then retry the import in DevKinsta.