Problem: 404 or blank page for docs
The documentation URLs live under /docs/. Verify that the /docs/index.php and its routing .htaccess are installed, and that the old blanket Require all denied rule has been replaced with the package’s safe, scoped rules.
Problem: XML opens but no ad plays
Opening VAST XML in a browser only confirms an XML response. Check that the player has VAST support and that the tag was entered into its advertising field, not its video source field. Try a single short commercial before an Ad Pod.
Problem: MP4 not found or video stays black
Check the <MediaFile> URL directly in a browser and its HTTP status, media type and codec. Wait for conversion to finish. Cross-origin requests, browser policies, expired files and unsupported codec/container combinations can break playback.
Problem: autoplay or sound fails
Mobile and desktop browsers commonly require user interaction before audible video playback. Initialize any IMA SDK based on user gesture and configure volume through the ad manager, not only a hidden HTML5 content element.
Problem: Pod plays only one ad
Your player may not support VAST 3.0 sequential Ad Pods. Verify multiple <Ad sequence="..."> elements in the XML and run a full test in an advertising SDK with documented pod support.
Problem: no impressions in Statistics
Confirm that the player actually fires the <Impression> beacon and that the beacon reaches the tracking endpoint. A request for the tag alone does not trigger an impression. A native <video> test preview also may not send the ad-tracking events.
Problem: HTTP 401 from /api/v1
This is expected when visiting the management API without a private Bearer key. Use the Developer API tab to create a key and call the API from an authenticated tool.
Problem: HTTP 500
A PHP server error needs a server-side log. Never display API secrets, filesystem credentials, or full bearer tokens in screenshots or bug reports.