Faqs

Troubleshoot Video Playback

Check playback in a fixed order so you can find the failing layer without weakening protection. Most issues come from publication state, an expired or malformed playback URL, an embed or browser restriction, or a mismatch between the project's protection settings and the page requesting playback.

Start with the asset and project

  1. Confirm the upload finished processing and the video is published.
  2. Verify that the embed or playback URL belongs to the intended video and project.
  3. Open the browser developer tools and record the player, network, or console error.
  4. Test the same video with a newly generated supported embed rather than a cached old copy.
  5. Confirm the selected project output and protection mode are supported by the test browser and device.

Check signed access and origin rules

For signed playback, verify the link has not expired and that your application generated it for the correct resource. Avoid logging or sharing the complete signed URL. For origin-restricted playback, add the exact approved website origin and keep the allow-encryption-keys-on-all-origins exemption disabled when domain enforcement is required.

Some page builders, webviews, casting devices, or iframe environments may omit or change request-origin information. Compare the supported iframe and JavaScript embeds on the same approved page. If one environment cannot supply the information your protection rule needs, select a documented integration for that environment instead of broadly opening key delivery.

Check browser and page behavior

  • Retry in a private window to separate the issue from stale cache or extensions.
  • Test a second supported browser and network.
  • Confirm the page is HTTPS and does not block required scripts or media with its security policy.
  • For autoplay, retry with muted playback or a viewer-initiated play button.
  • For subtitles or alternate audio, confirm the track is published and selected in the player.

Encryption or DRM errors

Confirm that the project uses the intended protection mode and that the current plan is entitled to it. AES-128 and DRM are alternative project modes. Check origin and signed-link inputs before changing the protection setting. Disabling encryption as a generic troubleshooting step can hide the configuration problem and expose content.

What should I send to support?

  • Video and project identifiers.
  • Page hostname and whether the embed is iframe, JavaScript, or a custom player.
  • Browser, version, device, operating system, and network.
  • Approximate time and timezone of the failure.
  • Exact error text plus a screenshot or sanitized network request.
  • Video Options
  • Video Player
  • Screen Recording & Download Prevention

Something missing or wrong here? Tell us and we will correct it. New to DynTube? Start with uploading and embedding.