Hallmark in Frndly (using Docker) stopped working a few dys ago: "The media could not be loaded, either because the server or network failed or because the format is not supported." My other Frndly channels seem to be working. Anyone else having this issue?
1 Like
HALLMARK is working here on my FRNDLY setup.
No problem.
I checked Channels to make sure it didn't fall over to TVE but it is working.
Not working for me either. Same problem, where Hallmark
channels get that error but all the other frndly channels seem to work. I use the python setup.
Hallmark works fine for me with frndly, just verified
This is the error that I got just now while trying to watch via the server-
The media could not be loaded, either because the server or network failed or because the format is not supported.
The log shows-
2026/02/15 11:01:01.007917 [ERR] Failed to start stream for ch9098: M3U: Could not fetch playlist from localhost:8183: GET: http://localhost:8183/play/hallmark_channel.m3u8: 500 Internal Server Error
2026/02/15 11:01:01.016237 [HLS] Couldn't generate master playlist for ch9098-dANY-ip192.168.1.110: M3U: Could not fetch playlist from localhost:8183: GET: http://localhost:8183/play/hallmark_channel.m3u8: 500 Internal Server Error
2026/02/15 11:01:01.016237 [HLS] Stopping transcoder session ch9098-dANY-ip192.168.1.110 (out=0s finished=false first_seq=0 last_seq=-1)
I am running this on a windows 10 pc with the extended service agreement (or whatever they call it)
When I tried to test the direct stream in my browser: http://localhost:8183/play/hallmark_channel.m3u8, I got an error message:
Error: Unsupported stream type: widevine (https://sr-live-hallmark1.akamaized.net/v1/dash/840a24ccd7c75076211d060179b3ad0c64fdc6ca/hallmark_sr/546d0d6bf2fc4257a70c4136a26b65b5/index.mpd?ads.dnt=1&ads.duration=7200&ads.rating=tvg&ads.us_privacy=1YYY&ads.gpp=DBABzw~1YYY~BVQVAAAAAAGA&ads.gpp_sid=7&ads.lmt=1&ads.app_bundle=com.tvapp.frndlytv&ads.app_store_url=https://play.google.com/store/apps/details?id=com.tvapp.frndlytv&ads.lat=1&ads.did=d36cc1c5-945b-32fa-ae11-d2e87e215a3f&ads.contenttype=live&ads.genre=comedy%255Fdrama%252CRomance%252Cchick%255Fflick&hdnts=st=1771215274~exp=1771236874~acl=!*/v1/dash/840a24ccd7c75076211d060179b3ad0c64fdc6ca/hallmark_sr/546d0d6bf2fc4257a70c4136a26b65b5/*!/payload/yupptvott_43_2778872_SHIELD30X8X4X0_US_24.211.137.187_frndlytv_1_channel_1_-1/*~data=yupptvott_43_2778872_SHIELD30X8X4X0_US_24.211.137.187_frndlytv_1_channel_1_-1~hmac=4cba4addc7a481400e60331a56584fa40197ddb2b1f0d30e51fabd0c62fab3cf&ads.network_name=Crown%20Media&ads.content_id=PTN30YCZRK&start=1771214400&startTime=1771214400).
Chat GPT says this means that Frndly has swiched Hallmark to a DASH (.mpd) stream that is protected by Widevine DRM. If that is the case, not sure why others are still getting the stream in the clear.
Looks like FRNDLY is going to be adding DRM soon to their channels.
I will check it here but due to the fact that they are cloud based servers. portionsof the streaming could have DRM while others won't have it.
Might want to keep this in the back of your mind.
Happened before and then they came back. Hopefully it's not permanent.
are you using the latest version of the code / container?
I pushed a change September 30 that would order multiple streams based on no drm instead of just blindly picking the first.
If its working for others then I suspect maybe the streams are [drm, non-drm] and your using older code that didn't sort before picking the first..
Otherwise, suspect it could be a rollout / A/B testing and you've been picked early
Yes, working fine for me.
Most likely the problem, indeed.
Hi guys,
glad the problem was sorted.
I would suggest preparing for the upgrade. Eventually, The owners of FRNDLY will make the change.
I suspect they wil need to perform extensive testing to make sure quality doesn't dorp too much and that a pool of supported devices will display the content properly.