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

# Troubleshooting

While we strive to provide a trouble-free website, sometimes things happen beyond our control. This helpful collection of articles covers a few problems you may encounter while using our website and instructions for troubleshooting and fixing them.

[**Unable to Log In**](/learning-more/troubleshooting/unable-to-log-in.md)\
Are you unable to log in to the website? Try these suggestions.

[**Popup-Blocking Software**](/learning-more/troubleshooting/website-functionality-issues.md#popup-blocking-software)\
Are you logged in, but certain features are not working correctly? This may be due to your popup-blocking software.

[**Slow Website Performance**](/learning-more/troubleshooting/website-functionality-issues.md#slow-website-performance)\
Is the website running slowly for you? There are several ways to figure out what might be causing the slowness.

[**Unusual Behavior**](/learning-more/troubleshooting/website-functionality-issues.md#unusual-behavior)\
Did none of the above fix the issues you're having? Here are some general troubleshooting steps to help you determine the problem and get it fixed.

{% hint style="success" %}
**Cool Tip:** Check out our [System Status](https://status.stockcharts.com/) page for more information on outages or site-wide issues.
{% endhint %}


---

# 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://help.stockcharts.com/learning-more/troubleshooting.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.