> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/support-and-troubleshooting/common-issues-and-solutions.md).

# Common Issues and Solutions

This section provides guidance for diagnosing and resolving common issues encountered while using Medianova CDN. Depending on the type of problem, you can follow the appropriate troubleshooting guide below.

Most configuration and operational issues can be investigated through the **Medianova Control Panel**, where you can review your CDN resource settings, cache policies, SSL/TLS configuration, security features, and available analytics.

**Medianova Control Panel:** <https://cloud.medianova.com>

If you cannot resolve the issue using these guides, contact the Medianova Support team.

**Support:** <support@medianova.com>

### Available Guides

#### [Troubleshooting Common Setup Issues](/support-and-troubleshooting/common-issues-and-solutions/troubleshooting-common-setup-issues.md)

Use this guide if you experience problems while configuring a CDN resource, including:

* SSL/TLS configuration
* Cache settings
* DNS configuration
* Origin connectivity
* Cookie handling
* WAF configuration

#### [Troubleshooting Performance Problems](/support-and-troubleshooting/common-issues-and-solutions/troubleshooting-performance-problems.md)

Use this guide if your CDN resource is already configured but you experience operational issues such as:

* Slow content delivery
* High origin latency
* Low cache hit ratio
* Unexpected HTTP status codes
* Performance degradation
* Traffic anomalies


---

# 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://clients.medianova.com/support-and-troubleshooting/common-issues-and-solutions.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.