# Gcore CDN > Gcore CDN delivers websites, files, and video from an origin through edge servers, configured per CDN resource. - [Overview](https://docs.gcore.com/cdn.md): Gcore CDN delivers websites, files, and video from an origin through edge servers, configured per CDN resource. - [How Gcore CDN works](https://docs.gcore.com/cdn/how-cdn-works.md): Gcore CDN delivery model covering the CDN resource, edge cache, origin group, origin shielding, and connections. ## Getting Started ## Create a CDN resource - [CDN resource overview](https://docs.gcore.com/cdn/getting-started/create-a-cdn-resource/overview.md): Compare Standard CDN and video delivery resource types, their features, use cases, and limits for delivering domains through Gcore CDN. - [Create a CDN resource](https://docs.gcore.com/cdn/getting-started/create-a-cdn-resource/create-a-cdn-resource.md): Create a Gcore CDN resource by setting up an origin group, adding a domain, and completing DNS with a CNAME record or delegated zone. - [Create a CDN resource for video streaming](https://docs.gcore.com/cdn/getting-started/create-a-cdn-resource/create-a-cdn-resource-for-video-streaming.md): Set up a Gcore CDN resource for video streaming with HLS, MPEG-DASH, HTTP-FLV, or MP4 delivery, plus origin shielding and secure tokens. ## Integrate CDN with CMS and other platforms - [CMS and platform integrations](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms.md): Guides for integrating Gcore CDN with content management systems, ecommerce platforms, forums, and cloud storage services. - [Use an AWS S3 static website as a CDN origin](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-aws-s3.md): Set up an AWS S3 static website as a Gcore CDN origin, configure a custom domain, and test content delivery. - [Integrate a CDN resource with b2evolution](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-b2evolution.md): Configure a Gcore CDN custom domain for b2evolution static assets by editing the advanced configuration file. - [Integrate a CDN resource with Cloudflare](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-cloudflare.md): Set up a Gcore CDN resource with Cloudflare by adding a DNS only CNAME record and matching origin settings. - [Integrate a CDN resource with Concrete CMS](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-concrete5.md): Integrate a Gcore CDN resource with Concrete CMS using the Use CDN add-on to serve static assets through a custom domain. - [Integrate a CDN resource with Craft CMS](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-craft.md): Configure a Gcore CDN domain as the Craft CMS filesystem base URL so asset URLs resolve through the CDN. - [Integrate a CDN resource with CS-Cart](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-cs-cart.md): Install the Universal CDN add-on in CS-Cart to rewrite image, CSS, and JavaScript URLs through a Gcore CDN domain. - [Integrate a CDN resource with Django CMS](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-django-cms.md): Configure Django CMS static and media URLs to serve assets through a Gcore CDN resource. - [Integrate a CDN resource with Drupal](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-drupal.md): Install and configure the Drupal CDN module to serve CSS, JavaScript, images, fonts, and videos through a Gcore CDN custom domain. - [Integrate a CDN resource with Google Cloud Storage](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-google-cloud-storage.md): Set up a Gcore CDN resource with a Google Cloud Storage bucket origin for public asset delivery through a custom domain. - [Integrate a CDN resource with IPB](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-ipb.md): Configure IP.Board 3.2 to 3.4 to serve images, CSS, and JavaScript from a Gcore CDN custom domain. - [Integrate a CDN resource with Invision Community Classic 4.x](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-ips.md): Configure Gcore CDN custom URLs for Invision Community Classic 4.x file storage and troubleshoot integration issues. - [Integrate a CDN resource with Joomla](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-joomla.md): Integrate a CDN resource with Joomla using the CDN for Joomla extension, covering setup, configuration, and troubleshooting. - [Integrate a CDN resource with Kirby](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-kirby.md): Integrate a Gcore CDN resource with Kirby by setting media and assets URLs to a custom domain. - [Integrate a CDN resource with Magento](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-magento.md): Configure Magento Open Source and Adobe Commerce to serve static and media files through a Gcore CDN resource. - [Integrate a CDN resource with Perch](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-perch.md): Integrate a Gcore CDN resource with Perch by updating config files and bucket paths to serve resources from a custom domain. - [Integrate a CDN resource with PrestaShop](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-prestashop.md): Configure a Gcore CDN resource as a PrestaShop media server to cache and deliver store images, theme files, and module assets. - [Integrate a CDN resource with PyroCMS 2.x](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-pyrocms.md): Configure a Gcore CDN resource custom domain in PyroCMS 2.x admin integration settings to serve static assets. - [Integrate a CDN resource with SocialEngine](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-socialengine.md): Configure a Gcore CDN resource with SocialEngine to cache and deliver static JavaScript and CSS files through a custom HTTPS domain. - [Integrate a CDN resource with TYPO3](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-typo3.md): Configure TYPO3 Replacer extension rules to serve generated assets and public files through a Gcore CDN resource. - [Integrate a CDN resource with vBulletin](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-vbulletin.md): Set up a Gcore CDN resource for self-hosted vBulletin 6, with caching rules for static assets and no-cache rules for private content. - [Integrate a CDN resource with Webasyst](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-webasyst.md): Connect a Gcore CDN resource to Webasyst by setting the CDN field to a custom domain and verifying asset URLs. ## Wordpress - [Integrate a CDN resource with WordPress using the Gcore plugin](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-gcore-plugin.md): Integrate a Gcore CDN resource with WordPress using the Gcore plugin, including URL rewriting and troubleshooting. - [Integrate a CDN resource with WordPress using WP Rocket](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-rocket-plugin.md): Configure WP Rocket to rewrite WordPress static asset URLs to a Gcore CDN custom domain for faster edge delivery. - [Integrate a CDN resource with WordPress using W3 Total Cache](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-w3-total-cache-plugin.md): Set up W3 Total Cache Generic Mirror to serve WordPress static files from a Gcore CDN custom domain. - [Integrate a CDN resource with WordPress using WP Super Cache](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/wordpress/integrate-cdn-resource-with-wordpress-wp-supercache-plugin.md): Configure a Gcore CDN resource with WordPress using the WP Super Cache plugin and its Simple CDN settings. - [Integrate a CDN resource with X-Cart 4.4.x](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-x-cart.md): Set up a Gcore CDN custom domain for X-Cart 4.4.x by editing PHP and Smarty files to serve skin, image, and cache assets. - [Integrate CDN resource with XenForo](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-cms/integrate-cdn-resource-with-xenforo.md): Configure XenForo externalDataUrl and javaScriptUrl to serve avatars, thumbnails, and JavaScript from a Gcore CDN custom domain. - [Extend CDN functionality with FastEdge](https://docs.gcore.com/cdn/getting-started/integrate-cdn-with-fastedge.md): Extend CDN functionality with FastEdge by attaching WebAssembly applications to request and response stages. ## Configure an origin - [Allow Gcore CDN access to an origin](https://docs.gcore.com/cdn/getting-started/configure-an-origin/add-cdn-servers-to-the-origin-acl-whitelist.md): Grant Gcore CDN edge servers access to a restricted origin using an HTTP auth header or public IP and network allowlists. - [Configure HTTP/2 on the origin](https://docs.gcore.com/cdn/getting-started/configure-an-origin/configure-http-2-on-the-origin.md): Configure HTTP2 on the origin server for Nginx and Apache to benefit clients connecting directly. - [CDN timeouts](https://docs.gcore.com/cdn/getting-started/cdn-timeouts.md): Gcore CDN timeout defaults for origin connections and client requests, including proxy read, connect, send, and keepalive values. - [About CDN resources interface: how it is arranged](https://docs.gcore.com/cdn/about-cdn-resources-interface-how-it-is-arranged.md): Overview of the Gcore CDN resources page covering creation, management, filtering, search, statuses, options, and deletion. - [Origin groups for CDN resources](https://docs.gcore.com/cdn/add-an-origin-group.md): Origin groups for CDN resources define multiple origins with load balancing, failover, and backup options for content delivery. ## CDN resource options ## General - [Specify an origin and the origin pull protocol](https://docs.gcore.com/cdn/cdn-resource-options/general/specify-an-origin-and-the-origin-pull-protocol.md): Set the CDN origin pull protocol to HTTP, HTTPS, or both, and assign an origin group for content fetching. - [Use a private bucket as an origin](https://docs.gcore.com/cdn/cdn-resource-options/general/use-a-private-bucket-as-an-origin.md): Configure a private S3 bucket as a CDN origin with authentication, origin groups, and credential rotation. - [Enable origin SSL validation](https://docs.gcore.com/cdn/cdn-resource-options/general/enable-origin-ssl-validation.md): Enable origin SSL validation for CDN by uploading a trusted CA certificate, retrieving its ID, and turning on validation for the resource. - [Set a custom domain for CDN](https://docs.gcore.com/cdn/cdn-resource-options/general/create-and-set-a-custom-domain-for-the-content-delivery-via-cdn.md): Set a custom domain for CDN static content, check DNS status, add extra domains, and point CNAME records to Gcore. - [Enable and configure origin shielding](https://docs.gcore.com/cdn/cdn-resource-options/general/enable-and-configure-origin-shielding.md): Enable origin shielding for a CDN resource and choose the shield location closest to the origin to reduce requests reaching it. - [Suspend a CDN resource automatically or manually](https://docs.gcore.com/cdn/cdn-resource-options/general/suspend-a-cdn-resource-automatically-or-manually.md): Suspend a CDN resource automatically after 90 days of inactivity or manually, and enable or delete it when needed. - [Customize connection and read timeouts](https://docs.gcore.com/cdn/cdn-resource-options/general/customize-connection-and-read-timeouts.md): Configure custom connection and read timeouts for Gcore CDN resources to control origin waits and avoid 504 Gateway Timeout errors. ## Cache - [CDN cache lifetime configuration](https://docs.gcore.com/cdn/cdn-resource-options/cache/specify-cache-lifetime-on-a-cdn-resource-or-origin.md): Configure CDN cache lifetime from origin headers or CDN settings, including custom expiry by response code and disabling caching. - [Set up a CDN resource to follow origin redirects](https://docs.gcore.com/cdn/cdn-resource-options/cache/set-up-a-cdn-resource-to-follow-origin-redirects.md): Configure a Gcore CDN resource to follow origin redirects and cache the target response for selected status codes. - [Specify cache lifetime for user browsers](https://docs.gcore.com/cdn/cdn-resource-options/cache/specify-cache-lifetime-for-user-browsers.md): Control browser caching for CDN resources by choosing origin controlled or CDN controlled cache lifetime. - [Ignore Set-Cookie or query string parameters when caching content on CDN servers](https://docs.gcore.com/cdn/cdn-resource-options/cache/ignore-the-set-cookie-or-query-string-parameters-when-caching-content-on-cdn-servers.md): Control how query string parameters and Set-Cookie headers affect CDN caching with ignore modes for cache keys. - [Always online: serve stale cache when the origin cannot provide a fresh response](https://docs.gcore.com/cdn/cdn-resource-options/cache/always-online-provide-the-stale-cache-if-the-origin-is-unavailable.md): Always Online serves stale cached content when the origin cannot provide a fresh response. - [Cache Sharding: share cache between CDN servers](https://docs.gcore.com/cdn/cdn-resource-options/cache/cache-sharding-share-cache-between-cdn-servers.md): Cache Sharding lets CDN servers in one PoP share cached content using consistent hashing to improve performance. - [Modify cache key](https://docs.gcore.com/cdn/cdn-resource-options/cache/modify-cache-key.md): Choose request variables that separate cached objects on a CDN resource and manage cache key modification settings. ## Access - [Control access to the content with country, referrer, IP, and user agents policies](https://docs.gcore.com/cdn/cdn-resource-options/security/control-access-to-the-content-with-country-referrer-ip-and-user-agents-policies.md): Limit CDN resource requests with country, referrer, IP, and user agent access policies using allow or block by default modes. - [Set up a redirect from HTTP to HTTPS](https://docs.gcore.com/cdn/cdn-resource-options/security/set-up-a-redirect-from-http-to-https.md): Redirect all HTTP requests for a CDN resource to HTTPS after enabling HTTPS and attaching an SSL certificate. ## Secure token - [About secure token](https://docs.gcore.com/cdn/cdn-resource-options/security/use-a-secure-token/about-secure-token.md): Gcore CDN Secure Token protects files from unwanted downloads by making links temporary or restricting access by IP address. - [Configure and use secure token](https://docs.gcore.com/cdn/cdn-resource-options/security/use-a-secure-token/configure-and-use-secure-token.md): Restrict CDN content access with a secure token using an MD5 hash and expiration timestamp, covering setup, signed URLs, and IP binding. - [Specify HTTP methods allowed for content requests from the CDN](https://docs.gcore.com/cdn/cdn-resource-options/security/specify-http-methods-allowed-for-content-requests-from-the-cdn.md): Restrict which HTTP methods a CDN resource accepts for content requests, allowing GET and HEAD and blocking others with 405 responses. - [Set the hostname passed in SNI requests to the origin](https://docs.gcore.com/cdn/cdn-resource-options/security/set-the-hostname-passed-in-sni-requests-to-the-origin-server.md): Configure the SNI hostname CDN servers send to the origin, choosing dynamic or custom modes for HTTPS origin pulls. - [Specify TLS versions allowed for content requests from the CDN](https://docs.gcore.com/cdn/cdn-resource-options/security/choose-tls-versions.md): Control which TLS protocol versions HTTPS clients can use for CDN content requests, with TLSv1.2 and TLSv1.3 recommended. ## Security - [Protect CDN resources with Gcore WAAP](https://docs.gcore.com/cdn/cdn-resource-options/cdn-security/protect-cdn-resources-with-waap.md): Enable Gcore WAAP for CDN resources to block malicious HTTP requests and create rules that turn protection off for specific URL paths. ## Compression - [Configure Gzip and Brotli compression](https://docs.gcore.com/cdn/cdn-resource-options/compression/configure-gzip-and-brotli-compression.md): Enable Gzip and Brotli compression for Gcore CDN resources, including precedence, requirements, and disabling Gzip. - [Configure fetch compression](https://docs.gcore.com/cdn/cdn-resource-options/compression/configure-fetch-compression.md): Enable Fetch compressed on a CDN resource so servers pull GZip content from the origin and serve it without decompressing. - [Configuring HTTP status codes for CDN-hosted content](https://docs.gcore.com/cdn/cdn-resource-options/specify-custom-http-status-code-for-the-content-delivered-by-the-cdn.md): Set custom HTTP status codes for CDN-hosted content, with scheduling and rule-based delivery for specific paths. - [Optimize large file delivery](https://docs.gcore.com/cdn/cdn-resource-options/optimize-large-file-delivery.md): Enable large file delivery optimization to cache CDN content in 10 MB chunks using HTTP range requests. - [Rewrite: redirect requests from the CDN to the origin](https://docs.gcore.com/cdn/cdn-resource-options/rewrite-redirect-requests-from-the-cdn-to-the-origin.md): Change CDN request paths before fetching from the origin with nginx rewrite rules and redirect flags. - [Proxy WebSocket connections to the origin](https://docs.gcore.com/cdn/cdn-resource-options/websockets-allow-permanent-connections-with-the-origin.md): Proxy WebSocket connections through Gcore CDN to the origin, with default settings for DNS delegation and CNAME resources. ## HTTP headers - [Specify HTTP headers that CDN adds to requests to the origin](https://docs.gcore.com/cdn/cdn-resource-options/http-headers/specify-http-headers-that-cdn-adds-to-requests-to-the-origin.md): Configure request headers that Gcore CDN adds to origin requests, including header names, values, and limits. - [Add the Access-Control-Allow-Origin header to the browser response](https://docs.gcore.com/cdn/cdn-resource-options/http-headers/add-the-access-control-allow-origin-header-to-the-browser-response.md): Configure CORS with the Access-Control-Allow-Origin header for Gcore CDN responses using resource settings, rules, or origin server. - [Add or hide response headers](https://docs.gcore.com/cdn/cdn-resource-options/http-headers/add-or-hide-response-headers.md): Add or hide CDN response headers in Gcore, including multiple values and hiding selected or all headers. - [Configure and check the host header](https://docs.gcore.com/cdn/cdn-resource-options/http-headers/configure-and-check-the-host-header.md): Set a custom or forwarded Host header for CDN origin requests and verify the origin accepts it. - [Identify the client protocol with X-Forwarded-Proto](https://docs.gcore.com/cdn/cdn-resource-options/http-headers/use-the-x-forwarded-proto-header-to-identify-the-protocol-used-for-cdn-servers-requests.md): X-Forwarded-Proto shows whether a client used HTTP or HTTPS to reach a Gcore CDN edge server. - [Network limits: set the content delivery speed to end users](https://docs.gcore.com/cdn/cdn-resource-options/network-limits-set-the-content-delivery-speed-to-end-users.md): Set a CDN download speed limit per connection with static or dynamic modes to control content delivery speed to end users. ## Image optimization (paid) - [About Image Stack](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/about-image-stack.md): Image Stack optimizes JPG and PNG images on the fly with quality, compression, resize, and crop operations on a CDN. - [Enable Image Stack](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/enable-image-stack.md): Enable Image Stack on a CDN resource or rule to optimize JPG and PNG images with quality, compression, resize, and crop settings. ## Image stack tools - [Configure image compression to WebP and AVIF](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/configure-image-compression-to-webp-and-avif.md): Convert JPG and PNG images to WebP or AVIF during CDN delivery to reduce file size without visible quality loss. - [Change image quality](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/change-image-quality.md): Reduce CDN image quality with Gcore Image Stack presets or URL query parameters for JPG and PNG delivery. - [Crop images](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/crop-images.md): Crop trims JPG or PNG images before CDN delivery using query parameters to set aspect ratio and crop location. - [Reduce image size](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/image-stack-tools/reduce-image-size.md): Reduce image size by adding Resize query parameters to image URLs, with Image Stack enabled on the CDN. - [Possible Image Stack errors](https://docs.gcore.com/cdn/cdn-resource-options/image-optimization-paid/possible-image-stack-errors.md): Diagnose Image Stack errors that break images or return originals, including compression, quality, resize, and crop operation failures. - [Query String Forwarding: forward parameters to sub-requests](https://docs.gcore.com/cdn/cdn-resource-options/query-string-forwarding.md): Query String Forwarding copies selected query parameters to nested HLS and MPEG-DASH manifests and segments on Gcore CDN. ## Rules for particular files - [Create a rule manually or from a template to configure settings for particular files](https://docs.gcore.com/cdn/cdn-resource-options/rules-for-particular-files/create-a-rule-manually-or-from-a-template-to-configure-settings-for-particular-files.md): Create CDN rules manually or from a template to override caching and other settings for specific files by URI pattern or regex. - [Create and use CDN rule templates](https://docs.gcore.com/cdn/cdn-resource-options/rules-for-particular-files/create-a-cdn-resource-rule-template-manually-or-use-a-system-one.md): Create custom and system CDN rule templates to preset file paths, origin pull protocols, and option overrides for rules. - [Block crawling of a CDN domain](https://docs.gcore.com/cdn/cdn-resource-options/rules-for-particular-files/set-robots-txt-to-avoid-adding-to-index-by-web-crawlers.md): Block web crawlers from crawling a CDN custom domain by returning a disallow robots.txt response. - [CDN cache purging and purge history](https://docs.gcore.com/cdn/clear-cdn-resource-cache-by-url-pattern-or-all.md): Clear CDN cache by URL, pattern, or all and review purge history for Gcore CDN resources. - [CDN billing](https://docs.gcore.com/cdn/how-the-cdn-service-and-its-additional-options-are-billed.md): CDN billing covers monthly traffic and request limits, overage charges, payment history, service suspension, and changing plans. ## IP configuration options - [Bring Your Own IP](https://docs.gcore.com/cdn/ip-configuration-options/byoip.md): Bring Your Own IP lets Gcore announce customer-owned IPv4 and IPv6 prefixes for CDN resources, using either a Gcore ASN or a customer ASN. - [Dedicated IP](https://docs.gcore.com/cdn/ip-configuration-options/dedicated-ip.md): Request a dedicated Gcore CDN IP or subnet to give a resource exclusive addresses and reduce shared IP reputation risks. - [CDN content prefetching](https://docs.gcore.com/cdn/load-the-content-to-cdn-before-users-request-it.md): CDN content prefetching loads files into cache before visitor requests, with limits and verification steps. ## Logs - [Logs Uploader](https://docs.gcore.com/cdn/logs/logs-uploader.md): Export CDN request and cache logs to S3, FTP, or SFTP destinations with Gcore Logs Uploader policies, targets, and configurations. - [Raw Logs export](https://docs.gcore.com/cdn/logs/raw-logs-export-cdn-resource-logs-to-your-storage.md): Raw Logs exports CDN request logs hourly to S3, FTP, or SFTP storage with statuses, intervals, and log fields. - [CDN resource logs in Log viewer](https://docs.gcore.com/cdn/logs/log-viewer-view-and-download-cdn-resource-logs.md): View and download CDN resource logs in Log viewer, filter requests by CNAME, IP, status, and export CSV or TSV. ## SSL certificates - [Add an SSL certificate to deliver content over HTTPS](https://docs.gcore.com/cdn/ssl-certificates/add-an-ssl-certificate-to-deliver-content-over-https.md): Attach an SSL certificate to a Gcore CDN resource to deliver content over HTTPS using a custom domain. - [Custom SSL certificate configuration](https://docs.gcore.com/cdn/ssl-certificates/configure-your-own-ssl-certificate.md): Upload a custom SSL certificate, attach it to a CDN resource, and manage renewal, expiration, and deletion. ## Let's Encrypt certificates - [Configure a Let's Encrypt certificate](https://docs.gcore.com/cdn/ssl-certificates/configure-a-lets-encrypt-certificate.md): Issue a free Let's Encrypt certificate for a CDN resource and fix an HTTP-01 failure. - [Use DNS-01 for a Let's Encrypt certificate](https://docs.gcore.com/cdn/ssl-certificates/use-dns-01-for-a-lets-encrypt-certificate.md): Enable DNS-01 for a Let's Encrypt certificate when HTTP-01 cannot reach the hostname. - [Renew or revoke a Let's Encrypt certificate](https://docs.gcore.com/cdn/ssl-certificates/renew-or-revoke-a-lets-encrypt-certificate.md): Renew or revoke a Let's Encrypt certificate that is already attached to a CDN resource. ## Terraform - [Manage CDN resources with Terraform v0](https://docs.gcore.com/cdn/terraform/manage-cdn-via-terraform.md): Manage CDN origin groups, resources, SSL certificates, and delivery options with Gcore provider v0 configuration files. - [Manage CDN with Terraform v2](https://docs.gcore.com/cdn/terraform/manage-cdn-via-terraform-v2.md): Provider v2 manages Gcore CDN resources, covering delivery options, presets, and migration from provider v0. ## Troubleshooting - [Common setup issues](https://docs.gcore.com/cdn/troubleshooting/common-setup-issues.md): Fix common CDN setup issues like 503 errors, redirect loops, host header problems, file downloads, and SSL certificate errors. - [Gcore CDN error status codes](https://docs.gcore.com/cdn/troubleshooting/gcore-error-status-codes.md): Gcore CDN error status codes explained, including 403, 404, 410, and other HTTP errors with causes and fixes. - [Traceparent header for troubleshooting](https://docs.gcore.com/cdn/troubleshooting/traceparent-header-for-troubleshooting.md): Use the Gcore CDN traceparent header to identify requests and correlate trace IDs in raw. - [Diagnose CDN routing and connectivity](https://docs.gcore.com/cdn/troubleshooting/diagnose-cdn-routing-and-connectivity.md): Identify the CDN edge handling requests, compare results across networks, and measure connectivity with Speedtest. - [Unavailable content after CDN resource creation](https://docs.gcore.com/cdn/troubleshooting/content-is-unavailable-after-a-cdn-resource-creation-how-to-solve-the-issue.md): Fix unavailable CDN content after resource creation by checking origin response, host header, DNS, SSL, and cache settings. - [Low cache hit ratio troubleshooting](https://docs.gcore.com/cdn/troubleshooting/cache-percentage-is-low-how-to-solve-the-issue.md): Troubleshoot a low CDN cache hit ratio by checking caching headers, traffic patterns, and common causes of origin fetches. - [Slow content delivery troubleshooting](https://docs.gcore.com/cdn/troubleshooting/content-delivery-speed-is-low-how-to-solve-the-issue.md): Troubleshoot slow CDN content delivery by comparing origin and edge speeds, checking cache hit ratio, and reviewing large file settings. - [An SSL certificate isn't working: how to solve the issue](https://docs.gcore.com/cdn/troubleshooting/an-ssl-certificate-isn-t-working-how-to-solve-to-issue.md): Troubleshoot SSL certificate errors including attachment failures, Let's Encrypt issuance problems, and TLS handshake issues. - [CDN 3xx response troubleshooting](https://docs.gcore.com/cdn/troubleshooting/3xx-error-how-to-solve-cdn-issues-with-redirect.md): Troubleshoot CDN 301 and 302 redirects by checking CDN settings, origin pull, Host header, and SNI before comparing response codes. - [CDN 4xx response troubleshooting](https://docs.gcore.com/cdn/troubleshooting/4xx-error-how-to-solve-cdn-issues-with-the-limited-access-and-content-non-existence.md): Troubleshoot CDN 4xx responses by checking status causes, origin content availability, resource settings, and response logs. - [CDN 5xx response troubleshooting](https://docs.gcore.com/cdn/troubleshooting/5xx-error-how-to-solve-server-issues.md): Troubleshoot CDN 5xx response errors by checking origin availability, CDN resource settings, pull protocol, Host header, and logs. ## Video CDN - [Video CDN Overview](https://docs.gcore.com/cdn/video-cdn/video-cdn-overview.md): Video CDN overview covers Gcore CDN video delivery, supported formats like HLS and DASH, low latency, security, and setup requirements. - [Common Media Client Data (CMCD)](https://docs.gcore.com/cdn/video-cdn/cmcd.md): Send Common Media Client Data (CMCD) v1 from video players to Gcore CDN for playback context in delivery logs. - [HLS and LL-HLS via CDN](https://docs.gcore.com/cdn/video-cdn/hls.md): Deliver HLS and low-latency HLS streams through Gcore CDN with cache rules, supported formats, and setup requirements. - [Improve video delivery speed for low-traffic accounts](https://docs.gcore.com/cdn/video-cdn/improve-video-delivery-speed.md): Speed up video delivery for low-traffic accounts by warming the CDN cache, prefetching popular content, and tuning cache TTL settings. - [DASH and LL-DASH via CDN](https://docs.gcore.com/cdn/video-cdn/dash.md): Deliver MPEG-DASH and low-latency LL-DASH live streams through Gcore CDN with Chunked-Proxy for 2 to 4 second latency. - [Multi-codec VOD delivery over CDN](https://docs.gcore.com/cdn/video-cdn/multi-codec-vod-delivery.md): Deliver HEVC, AV1, VP9, and H.264 VOD renditions over Gcore CDN to cut bandwidth while keeping H.264 fallback for older devices. - [Origin shielding for video delivery](https://docs.gcore.com/cdn/video-cdn/origin-shielding-for-video.md): Origin shielding for video delivery reduces origin requests for live events and VOD libraries by caching at a shield location. - [Secure Token for Video CDN](https://docs.gcore.com/cdn/video-cdn/secure-token.md): Secure Token for Video CDN protects HLS and MPEG-DASH streams with Query String Forwarding for manifests and segments. - [Auto-refresh CDN secure tokens](https://docs.gcore.com/cdn/video-cdn/secure-token-auto-refresh.md): Set short-lived CDN secure tokens to expire in 60 seconds and refresh them automatically in the player to stop link sharing. - [Troubleshoot video delivery](https://docs.gcore.com/cdn/video-cdn/troubleshoot-video-delivery.md): Diagnose video delivery issues such as 403 and 410 errors, buffering, 504 timeouts, live MPEG-DASH 404s, and CDN caching problems. - [HTTP-FLV Live and VOD Delivery](https://docs.gcore.com/cdn/video-cdn/flv-streaming.md): Configure HTTP-FLV live and VOD delivery on Gcore CDN with low-latency streaming, authentication, origin failover, and monitoring. - [CDN reports and overview](https://docs.gcore.com/cdn/view-statistics-of-a-cdn-resource.md): Track CDN performance, traffic, cache, errors, and security with Overview dashboards and statistics reports for Gcore CDN resources. ## Grafana - [View CDN statistics in Grafana](https://docs.gcore.com/cdn/grafana/view-cdn-statistics-in-grafana.md): Grafana panels for CDN traffic, cache efficiency, and request statistics.