CDN Plugin
The CDN plugin sends supported site assets, videos, and live-stream files through a content delivery network. This reduces repeated traffic to the AVideo server and can shorten the network distance to viewers.
The website, database, Encoder, and live server still need to operate normally. A CDN does not repair a missing or invalid video.
| Situation | What the CDN changes |
|---|---|
| Viewers are far from the server | Cached files can be served from a closer edge location |
| A popular video creates high outbound traffic | Repeated requests can leave from the CDN instead of the origin |
| A live event has many viewers | Supported live segments can be distributed beyond one origin connection |
| The server disk is filling | CDN delivery alone does not add storage; use CDN Storage separately |
- Sign in to the AVideo Marketplace, open CDN, and create the service for the correct site.
- In AVideo, sign in as an administrator.
- Open Admin → Plugins → CDN.
- Use the plugin's Edit/CDN button to open the service panel.
- Copy the assigned key and URLs into the matching private plugin parameters when they are not filled automatically.
- Keep
enable_cdnenabled, save, and clear the AVideo cache. - Test one public MP4, every HLS quality, an image, and live playback if used.
- In the browser network panel, confirm that supported files use the CDN hostname.
| Parameter | Purpose |
|---|---|
enable_cdn |
Turns CDN URL replacement on or off |
key |
Identifies/authenticates the configured CDN service |
CDN |
CDN URL used for normal supported assets and media |
CDN_Live / CDN_LiveServers
|
URLs used by supported live workflows |
enable_storage |
Also enables the storage workflow described in CDN Storage |
Keep keys, storage passwords, and private dashboard details out of screenshots and support tickets.
For the billing interface, see Add CDN credit. Rates vary by region and can change; use the current CDN price page for quotes.
| Feature | CDN delivery | CDN Storage |
|---|---|---|
| Reduces origin delivery traffic | Yes | Yes, through its CDN delivery |
| Stores the video library remotely | No | Yes |
| Replaces the AVideo application/database server | No | No |
| Needs usage credit | Yes | Yes |
Why do I still see requests to the origin? First requests, expired cache, private content, unsupported files, or a configuration error can still reach the origin.
Why did playback stop after the CDN was enabled? Recheck the configured hostname, HTTPS certificate, DNS/service status, account balance, and browser network error.
Can I disable it temporarily? Yes, but test origin capacity first. If storage is enabled, stored-video behavior is separate from normal CDN delivery.
Can someone configure it for me? Managed setup and migration assistance are available through professional support.