shopify theme dev fails to start or preview a password-protected Shopify store, check shopify version before changing store permissions. Shopify stopped supporting the legacy protected-store preview/session flow used by CLI 3.83.x and earlier in September 2026. Use CLI 3.84.0 or newer, preferably the current release.On this page
Why this happens
Some older tutorials troubleshoot this as a storefront-password problem and suggest removing the password. That can mask the actual issue: older CLI builds used an authentication path that Shopify retired for protected storefront development. The affected workflows include shopify theme dev, shopify theme console and some shopify app dev sessions involving theme app extensions.
Shopify’s August 27, 2026 notice specifically scopes this change to password-protected storefronts. A working CLI command against a public shop is not proof that the same CLI can preview a protected development shop.
What to change
Check the executable version in the shell, CI runner, or project-local package environment actually executing the command. Upgrade Shopify CLI, reopen the shell if your PATH still resolves an older executable, and authenticate using a supported Shopify account or Theme Access credentials. Keep the store password in place unless you independently intend to change access policy.
If a CI pipeline pins @shopify/cli, update its version and lockfile or install step; upgrading only your laptop will not fix CI. If a project has multiple package managers or globally installed binaries, inspect which executable runs. Don’t confuse the storefront password with a Theme Access token: they solve different problems.
Practical example
shopify version
npm install -g @shopify/cli@latest
shopify version
shopify theme dev --store your-store.myshopify.com
Run these from a valid theme project directory. Shopify’s current CLI documentation also describes --store-password for protected storefronts and --password for Theme Access credentials. Supply secrets through the appropriate environment or secret store, not committed scripts.
How to test this
- Capture the CLI version and failing command on the affected workstation or runner.
- Upgrade to a supported CLI version and confirm the version reported by the actual executable.
- Run theme dev against the same password-protected test store with the same authorized account.
- Verify preview URL, CSS/section hot reload, and theme editor synchronization as applicable.
- Run the same workflow in CI or on a teammate’s machine if those environments have independent CLI installations.
- Confirm the storefront remains password protected and no credentials were committed.

