That URL scheme is not supported
Only http and https can be fetched; schemes such as rtmp, rtsp and file cannot.
What it means
The URL uses a scheme other than http or https — commonly rtmp, rtsp, udp, rtp or file. These describe transports we have no way to open.
Why it matters
Neither a browser nor our server can open these. rtmp and rtsp need a dedicated client, udp and rtp only work on a network carrying that multicast, and file refers to the local disk of whatever machine opens it.
How to fix it
- For web delivery, repackage the source as HLS or DASH over HTTPS.
- To check a local file, paste its contents directly instead of a file:// URL.
Check your own stream
The free stream tester runs this check on every analysis and links each finding straight back here.
Open the stream tester →Frequently asked questions
- What does "That URL scheme is not supported" mean?
- The URL uses a scheme other than http or https — commonly rtmp, rtsp, udp, rtp or file. These describe transports we have no way to open.
- Why does it matter?
- Neither a browser nor our server can open these. rtmp and rtsp need a dedicated client, udp and rtp only work on a network carrying that multicast, and file refers to the local disk of whatever machine opens it.
- How do I fix it?
- 1. For web delivery, repackage the source as HLS or DASH over HTTPS. 2. To check a local file, paste its contents directly instead of a file:// URL.
- How do I confirm this is the origin and not the player?
- Run the URL through the stream tester, which reports the response the origin actually returned — status, headers, redirects and size — so you can separate a delivery fault from a manifest fault.
- What is the first thing to try?
- For web delivery, repackage the source as HLS or DASH over HTTPS.
Related Fetching and delivery checks
- The browser blocked the request (CORS)Your browser refused to read the response because the origin did not send an Access-Control-Allow-Origin header.
- The origin returned an error statusThe server answered with a 4xx or 5xx status instead of the manifest, so there was nothing to analyze.
- That address cannot be reached from our serversThe URL resolves to a private or reserved address, so we will not connect to it from the server. Local mode tests it from your own browser instead.
- That is not a valid URLThe address could not be parsed, so no request was attempted.
- The URL redirected too many timesWe follow up to three redirects; this URL exceeded that.
- The response was too largeThe document exceeded the size limit for a single analysis.