The request could not be completed
The connection failed before a response arrived.
What it means
DNS did not resolve, the connection was refused or timed out, or TLS negotiation failed.
Why it matters
Nothing was retrieved, so nothing could be analysed. Viewers on the open internet would hit the same wall.
How to fix it
- Check the hostname resolves publicly, not only inside your own network.
- A TLS failure usually means an expired certificate or a missing intermediate — browsers are stricter than curl about the chain.
- If the origin only accepts traffic from certain networks, use Local mode so the request comes from yours.
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 "The request could not be completed" mean?
- DNS did not resolve, the connection was refused or timed out, or TLS negotiation failed.
- Why does it matter?
- Nothing was retrieved, so nothing could be analysed. Viewers on the open internet would hit the same wall.
- How do I fix it?
- 1. Check the hostname resolves publicly, not only inside your own network. 2. A TLS failure usually means an expired certificate or a missing intermediate — browsers are stricter than curl about the chain. 3. If the origin only accepts traffic from certain networks, use Local mode so the request comes from yours.
- 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?
- Check the hostname resolves publicly, not only inside your own network.
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.
- 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.