> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/support-resources/troubleshooting-guides/generic/resolving-login-issues-in-a-normal-chrome-window.md).

# Resolving Login Issues in a Normal Chrome Window

<table><thead><tr><th width="174.5">Problem</th><th width="237.8333740234375" valign="middle">Cause</th><th>Instructions to Resolve</th></tr></thead><tbody><tr><td>Login to Avo Assure fails in a normal Chrome window but works in an Incognito window.</td><td valign="middle"><ul><li>Old or corrupted cookies affect the login process, especially after an upgrade, password change, or account or SSO switch.</li><li>Cached files from an older Avo Assure version interfere with the login process.</li><li>Browser extensions, such as ad blockers, privacy tools, or password managers, interfere with login requests.</li><li>A saved password is outdated, or the Chrome profile is corrupted.</li></ul></td><td><ul><li><strong>Clear site cookies and cache</strong>: On the Avo Assure login page, click the site information icon next to the URL, select <strong>Site settings</strong>, and click <strong>Delete data</strong>. Alternatively, go to Chrome <strong>Settings</strong> > <strong>Privacy and security</strong> > <strong>Delete browsing data</strong> and select <strong>Cookies</strong> and <strong>Cached images and files</strong>.</li><li>Close all Chrome windows and reopen Chrome. Try logging in again.</li><li><strong>Disable browser extensions</strong>: Go to <code>chrome://extensions</code> and turn off all extensions. Try logging in again. If login works, enable the extensions one at a time to identify the extension causing the issue. Allow the Avo Assure URL in the extension, if supported.</li><li><strong>Check saved passwords</strong>: Verify that the password manager does not autofill an outdated password. Enter the password manually or update the saved password.</li><li><strong>Try a new Chrome profile</strong>: Create a new Chrome profile and try logging in. If login works, use the new profile or reset the existing profile.</li></ul><p><strong>Note</strong>: After an upgrade, password change, or SSO change, press <strong>Ctrl + Shift + R</strong> to reload the login page without using the cached page resources.</p></td></tr></tbody></table>


---

# 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.avoautomation.com/avo-assure/support-resources/troubleshooting-guides/generic/resolving-login-issues-in-a-normal-chrome-window.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.
