I am able to login using Shopify CLI however unable to run it locally.
Getting SSL error. PFA screenshot.
Please let me know if anyone has solution.
Thanks.
Topic summary
-
Login via Shopify CLI succeeds, but running the local development environment fails with an SSL-related error (a screenshot was attached).
-
Another participant asked if the issue auto-resolved after ~24 hours, noting they saw delayed order processing in their logs during the incident. The original poster reported no auto-resolution or response.
-
Most recent update: Running “shopify theme dev -s ” now fails with the message “command theme:serve:. not found” and an AbortSilentError. The stack trace references @shopify/cli-kit (ruby.js) and yoga-layout-prebuilt, suggesting a CLI/internal dependency error rather than just SSL.
-
Context: Shopify CLI is the command-line tool for theme development; “theme dev/serve” starts a local dev server. SSL errors typically relate to certificate/TLS issues.
-
Outcomes/decisions: No fix, workaround, or official guidance was provided in the thread. No configuration changes or steps were confirmed to help.
-
Status: Unresolved/ongoing. Open questions include whether the problem is environmental (CLI/plugins/Node/Ruby dependencies) vs. a transient service issue, and whether others can reliably reproduce or confirm auto-resolution.
Did you find this auto-resolved about 24 hours later? Discovered this in our logs and found a number of orders that had delayed processing because of it.
NO I did not get any response or resolve.
Now getting this error while running -
shopify theme dev -s https://revel-moments-development.myshopify.com/
╭─ error ──────────────────────────────────────────────────────────────────────╮
│ │
│ command theme:serve:. not found │
│ │
╰──────────────────────────────────────────────────────────────────────────────╯
[email removed]
throw ex;
^
AbortSilentError
at execCLI2 (file:///C:/Users/a.a.arvind.kulkarni/AppData/Roaming/npm/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/public/node/ruby.js:47:15)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
tryMessage: null,
type: 1,
nextSteps: undefined
}