Delivery approaches
The table below shows where the two approaches differ:Billing
A custom CDN resource adds a separate per-GB bandwidth charge on top of the existing streaming costs — transcoding and storage remain covered by the streaming plan.Settings managed by Video Streaming
After support appliesStreaming Rules, the CDN resource is linked to Video Streaming, which serves almost all of its options, including the origin and origin group, the cache lifetime for each file type, and origin shielding. These options already hold the correct values for streaming delivery, so nothing needs to be specified for them. The Customer Portal can still show them as editable, but they cannot be adjusted because Video Streaming controls them, and the Access section is the one that changes the behavior of the resource.
Custom CDN resource setup
Video Streaming must be active before creating a custom CDN resource.1
Activate CDN product
- Log in to the Gcore Customer Portal
- Navigate to CDN in the main menu
- Click Activate CDN service if not already active
- Select a paid tariff that fits the bandwidth requirements
2
Create a CDN resource
- Navigate to CDN > CDN resources
- Click Create CDN resource
- Configure the resource:
- Origin source: the Video Streaming subdomain (e.g.,
12345.gvideo.io) - Add domain (optional): a custom domain for branded delivery (e.g.,
video.example.com)
- Origin source: the Video Streaming subdomain (e.g.,
- Click Create resource
- In the resource settings, set Origin pull protocol to HTTPS (General section)
3
(Optional) Configure access policies
- Navigate to CDN > CDN resources and select the resource
- In the left sidebar under Options, select Access
- Enable the policies needed for this resource. Each policy supports Allow by default (allow all except listed entries) and Block by default (block all except listed entries) modes:
For token-based access control, configure Video secure tokens separately — these are not in the Access section.
4
Request Streaming Rules
Gcore Support must apply
Streaming Rules to the CDN resource before streaming traffic is routed correctly. Provide the CDN resource ID and the streaming client ID when contacting support.5
Update application URLs
Once support confirms the setup is complete, replace
clientID.gvideo.io with the custom domain in all video URLs and verify playback:Multiple CDN resources
Multiple custom CDN resources pointing to the same streaming origin can each carry different access policies. This enables content segmentation without duplicating the stream:
Each resource has separate billing, monitoring, and policy configuration.
Troubleshooting
Most issues with custom CDN resources fall into one of the categories below. Check the CDN resource status in the Customer Portal before investigating further — an inactive resource causes all four.CDN resource not delivering content
If the CDN resource returns 404 or 502 errors, confirm that support has appliedStreaming Rules, verify the origin is set to the streaming subdomain, and confirm the CDN tariff is paid and active.