Cross-Origin Resource Sharing controls whether browser scripts can use responses from another origin. A media server can be reachable yet deny the webpage's request. The correct response headers must come from the service, not from a viewer's app settings.
Identify the browser-specific boundary
A native player is not governed by browser CORS in the same way. That explains why a stream can work in an app while a web player fails. It does not establish that either account or network has changed.
Report the blocked request type
The failure may concern a manifest, media segment, subtitle or authentication request. Redact credentials before sharing a console screenshot. The operator needs the resource type and page origin to investigate the policy.
Avoid unsafe proxy shortcuts
An unknown public proxy can expose account links and may not handle media reliably. Do not route private playlists through a random workaround. Ask for a supported browser player or a properly configured server response.
