> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/faqs/locksmith-wont-open.md).

# Locksmith won't open!

If Locksmith won't open from your store's admin, the cause is almost always a stale or blocked browser cookie, and the three steps below fix it in most cases.

You might see a blank screen, a spinning loader, an error message, or get sent back to a login page. Work through the steps in order and stop as soon as Locksmith opens.

### Step 1: Log in directly at uselocksmith.com/login <a href="#step-1-log-in-directly-at-uselocksmithcomlogin" id="step-1-log-in-directly-at-uselocksmithcomlogin"></a>

Signing in on Locksmith's own site refreshes your login cookie, which is often all it takes.

1. Open a new browser tab and go to <https://uselocksmith.com/login>.
2. Log in to the app.
3. Go back to your store's admin and open Locksmith again.

If it opens, you're done. If not, continue to Step 2.

### Step 2: Clear your browser cache and cookies, then try again <a href="#step-2-clear-your-browser-cache-and-cookies-then-try-again" id="step-2-clear-your-browser-cache-and-cookies-then-try-again"></a>

Clearing cached files and cookies removes the old data that can stop Locksmith from loading.

1. Open your browser's clear-data screen:
   * **Chrome / Edge:** press Ctrl+Shift+Delete (Cmd+Shift+Delete on Mac).
   * **Firefox:** press Ctrl+Shift+Delete (Cmd+Shift+Delete on Mac).
   * **Safari:** Settings → Privacy → Manage Website Data → Remove All.
2. Choose **All time** as the time range.
3. Tick **Cookies and other site data** and **Cached images and files**, then clear.
4. Close and reopen your browser.
5. Repeat Step 1: log in at <https://uselocksmith.com/login>, then open Locksmith from your store's admin.

Clearing cookies signs you out of most websites, including your store admin, so have your passwords handy.

### Step 3: Try a different browser <a href="#step-3-try-a-different-browser" id="step-3-try-a-different-browser"></a>

A fresh browser has no saved cookies or extensions, which rules out a problem with your usual one.

1. Open a browser you don't normally use, such as Chrome, Firefox, Edge or Safari.
2. Log in at <https://uselocksmith.com/login>.
3. Log in to your store's admin and open Locksmith.

If Locksmith works here, your original browser is likely blocking cookies, often through privacy settings or an ad-blocking extension. Allow cookies for uselocksmith.com there, or keep using the new browser.

### Still stuck? <a href="#still-stuck" id="still-stuck"></a>

Contact us (<team@uselocksmith.com>) and include these details so we can help!

* Your store's URL
* The browsers you tried, and their versions
* What you see when Locksmith fails to open (a screenshot helps)
* Which of the steps above you completed


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.locksmith.guide/faqs/locksmith-wont-open.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
