For the complete documentation index, see llms.txt. This page is also available as Markdown.

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, 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

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

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

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

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

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

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

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

Last updated

Was this helpful?