That is not a valid URL
The address could not be parsed, so no request was attempted.
What it means
The text supplied is not a URL our parser recognises, so the request was rejected before any network connection was attempted.
Why it matters
Nothing can be fetched until the address is well formed, so no diagnosis is possible. It is almost always a copy-and-paste artefact rather than a problem with the stream itself.
How to fix it
- Include the scheme: https://example.com/master.m3u8, not example.com/master.m3u8.
- Check for stray spaces or line breaks pasted along with the address.
- Non-ASCII characters in a hostname must be punycode-encoded.
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 is not a valid URL" mean?
- The text supplied is not a URL our parser recognises, so the request was rejected before any network connection was attempted.
- Why does it matter?
- Nothing can be fetched until the address is well formed, so no diagnosis is possible. It is almost always a copy-and-paste artefact rather than a problem with the stream itself.
- How do I fix it?
- 1. Include the scheme: https://example.com/master.m3u8, not example.com/master.m3u8. 2. Check for stray spaces or line breaks pasted along with the address. 3. Non-ASCII characters in a hostname must be punycode-encoded.
- 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?
- Include the scheme: https://example.com/master.m3u8, not example.com/master.m3u8.
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 URL scheme is not supportedOnly http and https can be fetched; schemes such as rtmp, rtsp and file cannot.
- 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.