CDN Resource is aimed to deliver static content (i.e. images, CSS files) via CDN servers.
CDN Resource allows caching content on CDN servers at a user's first request and storing it for further requests.
There is no restriction on the file size.
- Create a CDN resource
- Origin pull protocol
- Pull content from
- Custom domain (to create a CNAME record)
- SSL
How to create a CDN resource
Create a CDN resource
As soon as you sign up, go to the CDN section and click Create CDN resource.
There is a form on the page that includes the basic settings needed to create the resource.
Origin pull protocol
Origin pull protocol specifies the protocol that CDN servers use to pull content from an origin server
The parameter has three values: HTTP, HTTPS, HTTP, and HTTPS
Select Origin pull protocol, depending on which protocol the origin server uses to send the content.
HTTP - if the content on the origin server is available only via HTTP (port 80) or there is a redirect from HTTPS to HTTP on the origin server.
HTTPS - if the content on the origin server is available only via HTTPS (port 443) or here is a redirect from HTTP to HTTPS on the origin server.
HTTP and HTTPS - if the content on the origin server is available via both HTTPS and HTTP.
Learn more about the Origin pull protocol option.
Pull content from
Specify an origin or an origin group that CDN uses to pull the content from. The origin can be the IP address or your site domain.
- Select Single origin to specify a single origin.
- Select Origin group to specify multiple origins.
Uncheck the Use default port option and specify your own port if your origin does not work on the standard ports (80 and 443). 
Custom domain (to create a CNAME record)
Specify a custom domain that will be used on your site to deliver static content via CDN.
The parameter has two values: Custom value and gcdn.co zone (shared SSL).
Please, note! After creating a resource, you can't change the type of your custom domain or edit the first domain you specify.
- Select Custom value to specify your own domain. If necessary, add additional domains by clicking on the " + " in the domain line.
Please, note! The main and additional domains must be different from the origin.
After the resource is created, make changes to the DNS settings of the specified domain. Read the instructions below, in the section Setup guide.
- Select gcdn.co zone (shared SSL) to create a custom domain in the gcdn.co zone (only for the PRO 10TB tariff).
This value allows you not to register your own domain, but to create a free one in our domain gcdn.co zone. In this case, you do not need to configure DNS records and issue an SSL certificate, it is provided for free.
You can add additional domains in the gcdn.cozone by clicking on the " + " in the domain line.
Learn more about Custom Domain.
SSL
If you selected Custom value for the Custom Domain (to create a CNAME record) option, you can add your own SSL certificate for content delivery via CDN.
To do this, activate the Enable HTTPS option.
Please, note! You can get free Let's Encrypt certificate only after the resource created.
Add SSL certificate.
Learn more about your own and Let's Encrypt SSL certificates.
Setup guide
After the resource is created, a pop-up window will appear with a notification that you have successfully created the resource, click Open setup guide.
Please, note! If you decide to skip the setup guide at this step, you can always open it in the CDN resource settings.
Set up your DNS (optional step)
The Set up your DNS step is displayed if you selected Custom value for the Custom domain (to create a CNAME record) option at the CDN resource creation stage.
To deliver requests to your origin through CDN servers, it is necessary to redirect requests from the main and additional custom domains specified by you to the domain in our zone.
To do this, create a CNAME record in the DNS settings of the main and additional personal domains.
Please, note! If you don't know how to add a CNAME record, contact your DNS provider's technical support.
1. On the DNS provider's website, go to the DNS zone settings.
2. Create a CNAME record for both the main and additional custom domain:
- As the name/host specify the subdomains of the third and higher levels.
For example:
-
- For a three-level custom domain (i.e. three.two.one) use the third-level subdomain, here it is three.
- For the four-level custom domain (i.e. four.three.two.one) use subdomains of the third and fourth levels, here it is four.three.
- As the canonical name/destination to which requests will be redirected, specify the domain from the Set up your DNS step.
Note! Each account is assigned an individual domain, which is used for all the resources of the account.
For example:
- For the Custom domain (to create a CNAME record) option you have chosen Custom value and specified cdndomain.origin.com value.
- In this case, in the DNS settings of origin.com add a CNAME record with the name/host cdndomain and the canonical name/destination - cl-2f8fda65.gcdn.co - to which requests will be redirected.
To check whether the DNS settings are made correctly, click Check DNS setup status.
Click Next to proceed to the next step of configuring the resource.
Set up CDN resource step
Check additional settings to configure the CDN resource for your needs.
Follow the tips that match your project.
Click Next to proceed to the next step of configuring the resource.
Integrate with your project step
In this step, you need to integrate your project with the CDN.
- If you use automated site content management systems (CMS), such as WordPress, Joomla!, Drupal, use the instructions for plugins to integrate your project with the CDN.
If in our Knowledge Base there is no instruction for your CMS, use the manual integration instructions below or contact CMS support.
- If you do not use automated site content management systems (CMS), in paths to the static files replace an origin domain with the custom domain specified in the Custom domain (to create a CNAME record) option.
After your project is integrated with the CDN, check the availability of the content by clicking Check your integration.
If the check shows that the resource is Not integrated, the content is not delivered via CDN. Make sure that:
- You have successfully configured the DNS record in the Set up your DNS step, if you specified Custom value for the Custom domain (to create a CNAME record) option.
- The path of the static files is correctly changed, and the custom domain is specified in the static file URL instead of the origin domain.
If the check shows that the resource is Successfully integrated, the CDN resource configuration is complete.
As a result of the configuration, when the user opens a page e.g. https://carbonated-numerals.000webhostapp.com, static content placed on this page, for example, an image, is downloaded from CDN servers - from the address specified as a custom domain, in our case - cdndomain.gcdn.co.
