That monitor type is not recognised
A monitor must be one of hls, dash, m3u or epg.
What it means
The stored monitor names a kind we have no analyzer for, so the scheduler cannot decide how to interpret whatever the URL returns.
Why it matters
The scheduled check cannot run, so the monitor records an error on every interval and never produces a useful result. It also means any alerting attached to it is meaningless.
How to fix it
- Delete the monitor and recreate it choosing one of the supported types.
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 monitor type is not recognised" mean?
- The stored monitor names a kind we have no analyzer for, so the scheduler cannot decide how to interpret whatever the URL returns.
- Why does it matter?
- The scheduled check cannot run, so the monitor records an error on every interval and never produces a useful result. It also means any alerting attached to it is meaningless.
- How do I fix it?
- 1. Delete the monitor and recreate it choosing one of the supported types.
- 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?
- Delete the monitor and recreate it choosing one of the supported types.
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.