That address cannot be reached from our servers
The 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.
What it means
The hostname resolves to a loopback, private, link-local or otherwise reserved IP — 127.0.0.1, 192.168.x.x, 10.x.x.x or the cloud metadata address, for example. Our server refuses those.
Why it matters
A server that fetches arbitrary user-supplied URLs can be talked into reaching internal services on its own network — the standard server-side request forgery attack. Refusing private ranges, and re-checking after every redirect, is what stops that.
How to fix it
- Use Local mode. The analysis then runs entirely in your browser, which is on the same network as the stream, and neither the URL nor the results reach our servers.
- Alternatively paste the manifest text directly, which needs no fetch at all.
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 address cannot be reached from our servers" mean?
- The hostname resolves to a loopback, private, link-local or otherwise reserved IP — 127.0.0.1, 192.168.x.x, 10.x.x.x or the cloud metadata address, for example. Our server refuses those.
- Why does it matter?
- A server that fetches arbitrary user-supplied URLs can be talked into reaching internal services on its own network — the standard server-side request forgery attack. Refusing private ranges, and re-checking after every redirect, is what stops that.
- How do I fix it?
- 1. Use Local mode. The analysis then runs entirely in your browser, which is on the same network as the stream, and neither the URL nor the results reach our servers. 2. Alternatively paste the manifest text directly, which needs no fetch at all.
- How can I detect this automatically?
- Paste your stream delivery URL into StreamTest's free stream tester. It runs this check on every analysis, flags the finding, and links straight back to this page — no sign-up required.
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 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.
- The response was too largeThe document exceeded the size limit for a single analysis.