just a note of how its expected to work
There's a 3–5 second delay after a stream starts before the HLS URL is available. hls.js should automatically retry and connect once the files are ready.
I’m trying to play my stream from my domain using hls .js.
Your status endpoint returns:
{
"isLive": true,
"hlsUrl": "https://simulcast.me/hls/8e4551823a23f584/index.m3u8?apiKey=-zlqHdG0KoqskMKLfnCfsH9zfKZ8oOe-",
"streamKeyLabel": "test",
"playbackToken": "8e4551823a23f584",
...
}
But when my browser (or hls.js) requests that URL, I get:
Status: 404 Not Found
Content-Type: application/json; charset=utf-8
Body: JSON error (not an .m3u8 playlist)
Hls . js reports:
type: "networkError"
details: "manifestLoadError"
fatal: true
url: "https://simulcast.me/hls/8e4551823a23f584/index.m3u8?apiKey=..."
So your API says isLive: true with that hlsUrl, but the manifest URL returns 404.
Can you check why that HLS path doesn’t exist or why it’s returning JSON instead of the .m3u8 file
Discussion
I started a stream from OBS and kept it running.
The HLS URL
https:// simulcast . me/hls/8e4551823a23f584/index . m3u8?apiKey=...
loads in the Akamai hls .js player, but it only shows a black screen and stops after ~8 seconds even though OBS remains connected and streaming. No errors, just a short black clip.
Your client can reach his HLS.
The problem is the content/encoding, not your player.