> 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/troubleshooting-common-setup-issues.md). # Troubleshooting Common Setup Issues Configuration issues can affect cache efficiency, origin connectivity, security, and content delivery performance. This guide describes common setup problems encountered during CDN deployment and provides recommended troubleshooting steps. Most configuration-related issues can be investigated through the [**Medianova Control Panel**](https://cloud.medianova.com), where you can review your CDN resource settings, cache behavior, SSL/TLS configuration, security policies, and available analytics. ### SSL/TLS Configuration Issues #### Issue Clients receive certificate warnings or HTTPS connections fail. #### Possible Causes * Invalid or expired SSL certificate * Incorrect certificate assignment * Origin SSL configuration mismatch * Missing DNS records #### Resolution * Verify that the correct SSL certificate is assigned to the CDN resource. * Confirm that the origin server supports the selected TLS configuration. * Check that DNS records point to the CDN hostname. * Verify that the certificate covers all configured hostnames. **Related concepts** * [SSL Certificates](/products/security/ssl-tls-encryption/upload-and-manage-ssl-certificates.md) * [Origin SSL](/products/performance-cdn/static-content-delivery/advanced-configuration/cname-and-ssl.md) ### Cache-Control Configuration #### Issue Static assets are not being cached or cache hit ratio is unexpectedly low. #### Possible Causes * `Cache-Control: no-cache` * `Cache-Control: private` * Short cache lifetime * Conflicting cache directives #### Resolution * Cache only content that is safe to cache. * Avoid applying restrictive cache headers to static assets. * Configure appropriate cache expiration values. * Prefer consistent `Cache-Control` directives over conflicting cache policies. **Related concepts** * [Caching](/products/performance-cdn/static-content-delivery/advanced-configuration/caching.md) * [Edge Cache Expiration](/products/performance-cdn/static-content-delivery/advanced-configuration/caching/edge-cache-expiration.md) ### Cookie-Related Caching Issues #### Issue Static content is bypassing the cache because cookies are included in requests or responses. #### Resolution * Avoid sending `Set-Cookie` headers with cacheable static content. * Configure cookie handling according to your application's requirements. * Separate personalized content from static assets whenever possible. **Related concepts** * [Caching ](/products/performance-cdn/static-content-delivery/advanced-configuration/caching.md) * [Browser Cache](/products/performance-cdn/static-content-delivery/advanced-configuration/caching/browser-cache-rule.md) ### Origin Connectivity Problems #### Issue The CDN cannot retrieve content from the origin server. #### Common Symptoms * HTTP 502 * HTTP 503 * HTTP 504 #### Resolution * Verify that the origin server is reachable. * Confirm DNS resolution. * Check firewall rules. * Ensure the origin accepts connections from CDN edge servers. * Verify timeout settings. **Related concepts** * [HTTP Response Codes](/getting-started/concepts/http-response-codes.md) ### Cache Expiration #### Issue Content updates are not visible immediately, or objects expire too quickly. #### Resolution * Review Edge Cache Expiration settings. * Review Browser Cache settings. * Use Purge when immediate cache invalidation is required. * Ensure origin cache headers match the desired caching policy. **Related concepts** * [Edge Cache Expiration](/products/performance-cdn/static-content-delivery/advanced-configuration/caching/edge-cache-expiration.md) * [Browser Cache](/products/performance-cdn/static-content-delivery/advanced-configuration/caching/browser-cache-rule.md) * [Purge](/products/performance-cdn/static-content-delivery/advanced-configuration/purge.md) ### Web Application Firewall (WAF) #### Issue Legitimate requests are blocked unexpectedly. #### Resolution * Review configured WAF rules. * Check whether a managed rule triggered the request. * Verify custom rules and exceptions. * Test the request after adjusting the applicable security policy. **Related concepts** * [Web Application Firewall (WAF)](/products/security/web-application-firewall-waf.md) * [Managed Rules](/api-documentation/performance-cdn/page-rule.md) ### Rate Limiting #### Issue Clients receive **429 Too Many Requests** responses. #### Resolution * Review the configured rate limiting policy. * Verify request thresholds and burst limits. * Confirm that expected traffic patterns are not being blocked. **Related concepts** * [Rate Limiting](/products/security/rate-limiting.md) * [HTTP Response Codes](/getting-started/concepts/http-response-codes.md) ### DNS Configuration #### Issue Traffic is not reaching the CDN. #### Resolution * Verify CNAME records. * Confirm that DNS changes have propagated. * Ensure the configured hostname matches the CDN resource. **Related concepts** * [CNAME](/api-documentation/performance-cdn/cname-and-ssl.md) * [DNS Fundamentals](/products/dns.md) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://clients.medianova.com/support-and-troubleshooting/common-issues-and-solutions/troubleshooting-common-setup-issues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.