Skip to content

CSS CDN Integration and Playback Addresses โ€‹

Updated

Configure CSS CDN to use a StreamPackage endpoint as its origin. This is not simply a matter of swapping a domain string โ€” it is a process of verifying cross-service permissions, domain settings, DNS, certificates, and actual playback.

Prerequisites โ€‹

  • Have a StreamPackage channel and endpoint ready.
  • Confirm that CSS is enabled and that you have permission to use the playback domain.
  • Prepare domain ownership, DNS configuration permissions, and a HTTPS certificate.
  • Review the access policy of the origin endpoint.

Console Integration Steps โ€‹

  1. On the CDN tab of the StreamPackage channel details, review the Authorization procedure.
  2. Approve the service role permissions so that StreamPackage can configure CSS.
  3. Also confirm the permissions in the opposite direction, so that CSS can access the StreamPackage origin.
  4. Bind the playback domain. If the current screen directs you to the CSS console settings, follow that path.
  5. Register the CNAME you are given in DNS.
  6. Verify the HTTPS certificate and the origin request settings.

CSS playback domain with CNAME and the Enabled status

In addition to the Enabled status in the console, verify certificate validity and actual video playback.

Composing the Playback URL โ€‹

After binding the domain, replace the host of the endpoint URL with the playback domain and keep the path unchanged.

CategoryFormat example
Originhttps://PACKAGE_HOST/v1/CHANNEL/ENDPOINT/index.m3u8
CDNhttps://PLAYBACK_HOST/v1/CHANNEL/ENDPOINT/index.m3u8

Use the actual endpoint values for the path and file name. Origin access authentication and viewer access authentication are policies for different legs of the path.

API Integration Example โ€‹

Use the target channel ID and domain for API integration, and verify actual playback once it is connected.

bash
tccli mdp BindNewLVBDomainWithChannel --region ap-seoul \
  --ChannelId YOUR_CHANNEL_ID \
  --LVBDomain YOUR_PLAYBACK_DOMAIN

Comparing Origin and CDN โ€‹

bash
STREAM_ORIGIN_URL='https://PACKAGE_HOST/YOUR_ENDPOINT/index.m3u8'
STREAM_CDN_URL='https://PLAYBACK_HOST/YOUR_ENDPOINT/index.m3u8'
curl --silent --show-error --fail-with-body --max-time 20 "$STREAM_ORIGIN_URL"
curl --silent --show-error --fail-with-body --max-time 20 "$STREAM_CDN_URL"

Apply the required authentication to each. Once the master playlist opens, use the media URLs actually written inside it, and verify all the way through the segment requests.

SymptomWhat to check first
Verifying results starting from the originInput publishing, output destination, endpoint path, and origin authentication
Origin healthy / CDN 403Bidirectional service permissions, origin request Host / path / authentication, viewer access policy
TLSCertificate validity period, host name, certificate chain
Master healthy / verify results for child playlistsRelative URI resolution, request path, and query / header passthrough
Playlist stops updatingOrigin publishing state, cache policy for CDN playlists
Response timeDNS / network / origin latency and per-leg response times

For a 403 or access-related response, check the authentication, origin path, and permissions of that domain. After the configuration propagates, verify again along the same path.

Wrapping Up and Unbinding โ€‹

Confirm whether other viewers are using it, then unbind only the test connection.

bash
tccli mdp UnbindCdnDomainWithChannel --region ap-seoul \
  --ChannelId YOUR_CHANNEL_ID \
  --LVBDomain YOUR_PLAYBACK_DOMAIN

Unbinding may affect existing playback. Unnecessary channels / transfers and CDN usage are verified separately.

Built with VitePress ยท Deployed on Tencent EdgeOne Pages