DevKinsta DK0066 persistent issue on Apple Silicon – full environment reset already done

DevKinsta Installation
1

Hi DevKinsta team,

I’m reaching out because I’m completely stuck with a persistent DK0066 issue and I urgently need help to get this working as soon as possible.

I’m running DevKinsta on macOS (Apple Silicon / aarch64) with Docker Desktop, and I’ve gone through a full and exhaustive troubleshooting process, but the issue still persists.

Issue description

When creating a new site in DevKinsta, the process fails at different stages, but most consistently at:

  • Step 2 (initialization / setup stage)

  • Step 4 (“Downloading remote site”)

The error shown is always DK0066.

The behavior is inconsistent in terms of step, but the failure is always the same: the site creation process cannot complete.

What works

  • Docker Desktop is running correctly

  • All containers (nginx, php-fpm, adminer, mailhog) start successfully

  • docker ps runs without errors

  • No port conflicts detected (80, 443, 3306)

  • Network connectivity to Kinsta API is working (tested via curl – HTTP 301 response)

What I have already tried (extensive troubleshooting)

I have gone through a full reset of the environment:

Docker / system cleanup

  • Stopped all containers

  • Removed all containers and images

  • Removed all volumes (including devkinsta_db_data, dns, mailhog, ssh)

  • Pruned Docker system completely (system prune -a --volumes)

  • Reset Docker networks

  • Restarted Docker Desktop multiple times

  • Fully verified Docker daemon stability

DevKinsta reset

  • Completely removed ~/DevKinsta

  • Reinstalled DevKinsta from scratch

  • Performed multiple clean site creation attempts

Authentication / API

  • Confirmed no manual API token was initially configured

  • Verified login session issues and re-authenticated

  • No external API errors detected

System / network checks

  • No VPN active

  • No firewall blocking detected

  • Proxy disabled in Docker Desktop

  • macOS reboot performed multiple times

Logs summary

  • PHP-FPM containers start correctly and remain stable

  • MariaDB starts but often does not reach a clearly stable “ready for connections” state

  • Repeated log pattern: mysqld starting as process 1...

  • DevKinsta sync/download step fails consistently with DK0066

Current situation

At this point, I have completely rebuilt the environment multiple times. Docker itself is stable and functioning, but DevKinsta still fails during site provisioning and remote download steps.

I’m honestly running out of options here and I’m quite desperate to get this working because I rely on this environment for development work.

Request

Could you please confirm:

  • Is there a known issue with DK0066 on Apple Silicon (aarch64)?

  • Is there any incompatibility with current Docker Desktop versions?

  • Could this be related to the DevKinsta provisioning/sync engine itself?

  • Is there any workaround or stable version that works reliably?

Any help would be massively appreciated. I really need to get this working ASAP.

Thank you in advance.

(main.log redacted)

4

Hi @Tech_Aticco :waving_hand:

Welcome to the Kinsta Community!

I’m sorry to hear you’re experiencing these issues. Upon reviewing the man.log file, I noticed an error that seems to trigger the DK0066 message.

[2026-04-28 10:42:26.845] [error] [ipcMainStep] Error in operation SITE_CREATION, step database: Error: Error (1): UERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)

Could you please try the solution suggested in this other thread? You can find it here: Error: Something bad happened - when trying to import site from myKinsta - #15 by VladimirM

Let us know how it goes!

5

A few quick things worth trying before assuming a full bug:

  • Make sure Docker Desktop is set to use Rosetta for x86_64 images (if available)

  • Try increasing Docker resources slightly (CPU/RAM) to avoid MariaDB timeout during init

  • Test with a very minimal new site (no remote import) to isolate whether the failure is sync-specific

  • If possible, try an older DevKinsta version to rule out a recent regression