Why the browser blocks a request
CORS lets a server specify which origins can read a response in a browser. Opening a URL in a tab does not prove that a player can read it from another origin.
Find the failed request
- Open browser developer tools and the Network and Console tabs.
- Start playback and identify the blocked request: MPD, audio/video segment or license.
- Check the HTTP status and console message. Certificate, DNS, codec or authentication errors are not fixed simply by changing CORS.
- If you control the server, check whether Access-Control-Allow-Origin permits the LinkPlay origin. For preflight requests, OPTIONS must allow the required method and headers.
The fix belongs on the server
Ask your stream provider to configure CORS for the relevant manifest, segments and license endpoint. With credentials, a wildcard origin (*) is not enough: the server must allow the specific origin and necessary credentials.
LinkPlay sends requests from your browser. It has no proxy to bypass server permissions. Disabling browser security is not a fix for making a stream work for users.
Share diagnostics without secrets
Record the origin, request type, HTTP status and error message. Remove token-bearing query strings and Authorization headers before sharing screenshots or logs. Never include playback keys or private license responses.
Technical reference: MDN — Cross-Origin Resource Sharing
Open App