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.
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.
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:
Close DevKinsta completely and make sure it is fully shut down
Open Docker and delete only the containers that start with devkinsta_
Please do not delete the volumes, and do not remove any other containers that are not related to DevKinsta
Start DevKinsta again so it can recreate the containers
I was working with @ShawnC and we were able to resolve the file permissions issue at the server where the .quarantine files were living in both live and dev environments. Once those were removed, the site copied down to local without any issues.