Jump to content

M3U Plugin - Playback Error: no compatible streams


Go to solution Solved by sectune,

Recommended Posts

Posted (edited)

Dear all,

 

I hope you can let me know what I am doing wrong here.

I have an .m3u URL (tested working with VLC) with all my iptv channels. Emby M3U plugin is simply refusing to play any of the channels (channels get imported fine, I also seeing the channel logo and the epg xml source form separate URL is also applied correctly).

 

I will gladly share the iptv m3u for you to test (send me a DM or write here and we will figure sth out).

 

I am running 4.7.11.0 on my x86 QNAP in a docker container. Transcoding is enabled and working fine.

 

Any help is very much appreciated!

@Lukethank you very much for Emby and for the ongoing support!

 

Extract form debug log when I try and open one channel:

2023-01-29 19:53:54.172 Info LiveTvManager: Opening channel stream, external channel Id: m3u_9750615dfa2f399fd459840a1b2c89565099
2023-01-29 19:53:54.172 Info LiveTV: Streaming Channel m3u_9750615dfa2f399fd459840a1b2c89565099, with streamId: a3a924a4ababa42d6c1d59427eb41f13
2023-01-29 19:53:54.327 Error LiveTV: Error in GetChannelStreamWithDirectStreamProvider
2023-01-29 19:53:54.172 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 40000000, max bitrate: 1500000
2023-01-29 19:53:54.172 Info App: Bitrate exceeds DirectStream limit: media bitrate: 40000000, max bitrate: 1500000
2023-01-29 19:53:54.172 Info App: RemoteClientBitrateLimit: 9000000, RemoteIp: host1, IsInLocalNetwork: False
2023-01-29 19:53:54.172 Info LiveTvManager: Opening channel stream, external channel Id: m3u_9750615dfa2f399fd459840a1b2c89565099
2023-01-29 19:53:54.172 Info LiveTV: Streaming Channel m3u_9750615dfa2f399fd459840a1b2c89565099, with streamId: a3a924a4ababa42d6c1d59427eb41f13
2023-01-29 19:53:54.173 Info SharedHttpPipelineSource: Opening SharedHttpPipelineSource Live stream from http://host3/x_path4_x/x_path2_x?token=x_secret2_x
2023-01-29 19:53:54.173 Info HttpClient: GET http://host3/x_path4_x/x_path2_x?token=x_secret2_x
2023-01-29 19:53:54.325 Info HttpClient: Http response 403 from http://host3/x_path4_x/x_path2_x?token=x_secret2_x after 152ms. HeadersConnection=keep-alive, Date=Sun, 29 Jan 2023 18:53:52 GMT, Server=Streamer 22.05.1, X-Route-Time=23892, X-Run-Time=416, Access-Control-Allow-Origin=*, Access-Control-Allow-Methods=GET, PUT, DELETE, OPTIONS, Access-Control-Expose-Headers=Server, range, X-Run-Time, X-Sid, Content-Length, Location, Access-Control-Allow-Headers=x-vsaas-session, x-no-redirect, origin, authorization, accept, range, content-type, x-add-effective, session, x-originator, X-Deny-Reason=deny_backend
2023-01-29 19:53:54.327 Error LiveTV: Error in GetChannelStreamWithDirectStreamProvider
*** Error Report ***
Version: 4.7.11.0
Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
Operating system: Linux version 5.10.60-qnap (root@U16BuildServer116) (x86_64-QNAP-linux-gnu-gcc (toolchain config: [gcc-4.9.2 binutils-2.25 glibc-2.21]) 4.9.2, GNU ld
Framework: .NET 6.0.8
OS/Process: x64/x64
Runtime: system/System.Private.CoreLib.dll
Processor count: 8
Data path: /config
Application path: /system
MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Forbidden
at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)
at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod)
at Emby.LiveTV.TunerHosts.SharedHttpPipelineSource.OpenStream(IDisposable connectionContext, MediaSourceInfo mediaSource, String url, MediaProtocol protocol, CancellationToken cancellationToken, Int32 recursion)
at Emby.LiveTV.TunerHosts.SharedHttpPipelineSource.Open(CancellationToken openCancellationToken)
at MediaBrowser.Controller.LiveTv.BaseTunerHost.GetChannelStream(TunerHostInfo tuner, BaseItem dbChannnel, String tunerChannelId, String mediaSourceId, List`1 currentLiveStreams, CancellationToken cancellationToken)
at Emby.LiveTV.EmbyTV.GetChannelStreamWithDirectStreamProvider(BaseItem dbChannel, String providerChannelId, String streamId, List`1 currentLiveStreams, CancellationToken cancellationToken)
Source: Emby.Server.Implementations
TargetSite: Void MoveNext()

2023-01-29 19:53:54.328 Error MediaSourceManager: Error opening live stream
*** Error Report ***
Version: 4.7.11.0
Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
Operating system: Linux version 5.10.60-qnap (root@U16BuildServer116) (x86_64-QNAP-linux-gnu-gcc (toolchain config: [gcc-4.9.2 binutils-2.25 glibc-2.21]) 4.9.2, GNU ld
Framework: .NET 6.0.8
OS/Process: x64/x64
Runtime: system/System.Private.CoreLib.dll
Processor count: 8
Data path: /config
Application path: /system
MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Forbidden
at Emby.LiveTV.EmbyTV.GetChannelStreamWithDirectStreamProvider(BaseItem dbChannel, String providerChannelId, String streamId, List`1 currentLiveStreams, CancellationToken cancellationToken)
at Emby.LiveTV.LiveTvManager.GetChannelStream(String id, String mediaSourceId, List`1 currentLiveStreams, CancellationToken cancellationToken)
at Emby.Server.Implementations.Library.MediaSourceManager.OpenLiveStreamInternal2(LiveStreamRequest request, CancellationToken cancellationToken)
Source: Emby.Server.Implementations
TargetSite: Void MoveNext()
 
Edited by sectune
Posted

Hi, looks like your provider is sending back a Forbidden response. If you can get to the bottom of this then that should resolve your issue.  You may need to disguise the server using the user agent and/or referrer options.

Posted
10 minutes ago, Luke said:

Hi, looks like your provider is sending back a Forbidden response. If you can get to the bottom of this then that should resolve your issue.  You may need to disguise the server using the user agent and/or referrer options.

Dear luke, I tried with several different user-agents and also one referrer (although there is no instructions on the provider page to use). I also doubt that this provider is blocking Emby/Kodi as they provide a special format for Kodi on the page. Would you mind if I would send you the .m3u list in question so you can check?

Posted

Regardless they are rejecting the request with a 403 forbidden error so we can't proceed until we know why and how to get past that.

Posted (edited)

Thank you so much for your fast replies. I wish I could debug this further, any idea how I could proceed? I also sent you a DM. Maybe I am also not entering the correct syntax for the user-agent field? I have tried with:

#1:

VLC media player 3.0.2 Vetinari (revision 3.0.2-0-gd7b653cf14)

#2:

Mozilla/5.0 (Macintosh; Intel Mac OS X 13_2) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15

Maybe I am doing something wrong?
image.thumb.png.db9050abe79fca9542578379a81068b7.png

Edited by sectune
mickle026
Posted

The domain probably needs client headers, IE the m3u base URL as a referrer and maybe even a defaultrequestheader- accept string to get past this.

Usually the domain as referrer is enough

Try putting the base http address in the second box http://my-m3u-url.com/

 

BillOatman
Posted

Is there some reason you can't ask the provider or the m3u what they require?

Posted (edited)

Dear @mickle026, Dear @BillOatman,

thank you for your replies as well. I have tried with several base urls, also with the base url which is in the url of my m3u file. I did ask the provider and they actually sent me back the instructions on how to set it up with the PVR Simple IPTV Kodi plug-in. Using the Kodi plug-in is working without any issue and all I need to do in that Kodi plugin is provide the m3u url and the xmltv guide url, no shenanigans with custom header/user-agent. Just two plain and simple urls.

Simple IPTV Kodi Plug-in is basically an identical plug-in functionality-wise as the M3U Plugin in Emby, this is getting very frustrating as it seems to work in an almost identical setup, just not using Emby. And yes, I did try the Kodi user-agent: Kodi/16.1 (Windows NT 10.0; WOW64) App_Bitness/32 Version/16.1-Git:20160424-c327c53

I am out of ideas.

I already sent @Lukea DM with further information and I can for sure test and try to debug further if anyone got any more ideas how to do so. Please feel free to reach out via DM to me if you want to test yourself and help me figure out what's wrong here.

 

Maybe I am using the wrong user-agent? Anyone knows what is the default user-agent Kodi Simple IPTV plug-in uses? I checked in the GitHub commits but cannot easily decipher the most recent user-agent used there.

 

Thank you once again!

Edited by sectune
  • Solution
Posted

Sorry to reply to my own issues, I have finally diagnosed and found out the culprit and wanted to write it down here in case someone has a similar issue in the future. As Emby is routed through a VPN on my server, my IPTV provider is blocking based on my VPN server IPs. As soon as a deactivate the VPN connection routing everything starts to work perfectly. Thank you all!

  • Thanks 2
Posted

Thanks for following up.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...