> For the complete documentation index, see [llms.txt](https://docs.korewireless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.korewireless.com/kore/troubleshooting/troubleshooting/unable-to-login.md).

# Unable to Login

If you're having trouble logging into your account, follow these steps to resolve the issue:

1. **Check Your Login Credentials**
   1. Ensure you’re using the correct email address or username.
   2. Ensure that the account you are using is not blocked or disabled.
   3. Verify your password is entered correctly (case-sensitive).
   4. If you don't remember your password, try resetting it using the "Forgot Password?" button.
2. **Clear Browser Cache and Cookies**
   1. Clear your browser's cache and cookies, then try logging in again.
   2. Alternatively, try using a different browser or device.
3. **Contact Support**\
   If the issue persists, contact our customer support team. Provide details such as the error message and steps you've already tried.
   1. **Contact Us:** Visit our [Shop portal](https://shop.korewireless.com/) and click the **Contact Us** form. Fill in the relevant information and submit the form.  
   2. **Email:** <support@korewireless.com>


---

# 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://docs.korewireless.com/kore/troubleshooting/troubleshooting/unable-to-login.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.