There is no session to save this to
Saving needs either an account or a working session cookie.
What it means
Results are attributed to a signed-in user or to an anonymous session cookie. Neither was present on this request.
Why it matters
Every stored result belongs to someone, so that only they can read it back. A result with no owner could not be retrieved or deleted, so we decline to write one rather than leave an orphan.
How to fix it
- Allow cookies for this site; the anonymous session is a single httpOnly cookie.
- Or sign in, which keeps history across devices and browsers.
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 "There is no session to save this to" mean?
- Results are attributed to a signed-in user or to an anonymous session cookie. Neither was present on this request.
- Why does it matter?
- Every stored result belongs to someone, so that only they can read it back. A result with no owner could not be retrieved or deleted, so we decline to write one rather than leave an orphan.
- How do I fix it?
- 1. Allow cookies for this site; the anonymous session is a single httpOnly cookie. 2. Or sign in, which keeps history across devices and browsers.
- 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?
- Allow cookies for this site; the anonymous session is a single httpOnly cookie.
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.