Intermittent "No Compatible Streams..." Error (STRM files)

[sundevil67 28]

I'm posting this in the "web app" section, but it happens in every version of Emby I use (iOS, Samsung TV, Fire Stick).

"No compatible streams are currently available. Please try again later or contact your system administrator for details."

Content that plays fine in my IPTV provider's native app frequently throws this playback error when I try to open the STRM in Emby. Sometimes the URLs will work in VLC, but have the same playback error occur in Emby. I've played with every setting I can think of, but it is really hard to diagnose, as it seems to happen intermittently. I'm not seeing the failure recorded in my log at all.

If anyone can point me in the right direction toward a likely cause... 

 

 

[Luke 42114]

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

[sundevil67 28]

Strangely, I don't see anything related in the logs; maybe you'll notice something I don't. It references the transcoding-temp directory, but there are no new entries in there. It just happens on totally random episodes, many that used to work just fine. 

Thank you.

embyserver.txt.zip

[Luke 42114]

The remote server hosting the content is returning a 500 error code. Can you ask them why?

[Luke 42114]

Also what device on your network uses 192.168.0.108 ?

[sundevil67 28]

That IP address looks like my Mac Mini / Emby Server. 

I can’t say that my provider is blameless all of the time, or that my ISP never sneaks in & siphons some bandwidth, or that my VPN can be 100% counted on for consistent speed. Emby can randomly choke on a show the provider’s native app can play. It might work the next day. Finding a direct cause/effect has been impossible, but I may have stumbled upon a bit of helpful diagnostic info last night. Let's forget about the STRM files for a second...
 
I was watching a recording using the Samsung app, & the spinning wheel of despair showed up.. Emby was behaving as if I was trying to render a 3D feature-length 3D. I switched over to my Mac Mini & popped open the (local .ts) file with VLC. The app was speedy, responsive, and the playback flawless. Does that tell you anything? Is there anything else I can try? ChatGPT was directing me to adjust transcoding settings that I couldn't actually find. Thanks for the assist... 
 

[Luke 42114]

On 2/23/2026 at 1:10 PM, sundevil67 said:

That IP address looks like my Mac Mini / Emby Server. 

I can’t say that my provider is blameless all of the time, or that my ISP never sneaks in & siphons some bandwidth, or that my VPN can be 100% counted on for consistent speed. Emby can randomly choke on a show the provider’s native app can play. It might work the next day. Finding a direct cause/effect has been impossible, but I may have stumbled upon a bit of helpful diagnostic info last night. Let's forget about the STRM files for a second...
 
I was watching a recording using the Samsung app, & the spinning wheel of despair showed up.. Emby was behaving as if I was trying to render a 3D feature-length 3D. I switched over to my Mac Mini & popped open the (local .ts) file with VLC. The app was speedy, responsive, and the playback flawless. Does that tell you anything? Is there anything else I can try? ChatGPT was directing me to adjust transcoding settings that I couldn't actually find. Thanks for the assist... 
 

This does not indicate anything. Before emby server can try to transcode the stream, first it has to be able to pull it in. It can't do that if the remote server is sending back a 500 error code. This needs to be resolved first.