Jump to content

Recommended Posts

Valdorama
Posted

I'm trying to evaluate Emby to use as a DVR and client for IPTV. I've been using IPTVEditor to trim and organize the set of channels from the IPTV provider. I've configured Emby so that both the channel source and guide is provided via IPTVEditor links. Emby processes the channel list OK but it cannot seem to handle the XMLTV guide data. This guide data works in other IPTV apps so I don't think the problem is the data. I see this in the Emby logs:

2025-04-21 22:56:54.642 Info TaskManager: Executing Refresh Guide
2025-04-21 22:56:54.642 Info Server: http/1.1 Response 200 to host1. Time: 48ms. POST http://10.0.0.2:8096/emby/LiveTv/ListingProviders?ValidateListings=true&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=5c7d3dea-ab10-4cf8-a5ee-4e7647f826da&X-Emby-Client-Version=4.8.11.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json
2025-04-21 22:56:54.644 Info HttpClient: POST https://mb3admin.com/admin/service/registration/validate
2025-04-21 22:56:54.645 Info HttpClient: GET https://opop.pro/x_path1_x
2025-04-21 22:56:54.761 Info HttpClient: Http response 200 from https://mb3admin.com/admin/service/registration/validate after 117ms. Headers Server=nginx, Date=Mon, 21 Apr 2025 22:56:54 GMT, Connection=keep-alive, Access-Control-Allow-Origin=*, Access-Control-Allow-Headers=Content-Type, Range, Accept, X-Emby-Token, X-Admin-Token, X-Application, Access-Control-Allow-Methods=GET, POST, PUT, DELETE, OPTIONS, Cache-Control=no-store, must-revalidate, no-cache, Pragma=no-cache, Vary=Accept-Encoding
2025-04-21 22:56:54.763 Info SecurityManager: Registered for MBSupporter
2025-04-21 22:57:00.897 Info HttpClient: GetTempFileResponse url: https://opop.pro/x_path2_x
2025-04-21 22:57:00.897 Info HttpClient: GET https://opop.pro/x_path2_x
2025-04-21 22:57:03.023 Error LiveTvManager: Error getting channels
*** Error Report ***
Version: 4.8.11.0
Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
Operating system: Linux version 6.8.0-52-generic (buildd@lcy02-amd64-046) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubunt
Framework: .NET 6.0.36
OS/Process: x64/x64
Runtime: system/System.Private.CoreLib.dll
Processor count: 2
Data path: /config
Application path: /system
System.Xml.XmlException: System.Xml.XmlException: Unexpected end of file has occurred. The following elements are not closed: tv. Line 1, position 2862229.
at Emby.XmlTV.XmlTvProvider.GetXmlDataCache(ListingsProviderInfo info, CancellationToken cancellationToken)
at Emby.XmlTV.XmlTvProvider.GetChannels(ListingsProviderInfo info, CancellationToken cancellationToken)
at Emby.LiveTV.EmbyTV.RefreshEpgChannels(IListingsProvider provider, ListingsProviderInfo info, CancellationToken cancellationToken)
at Emby.LiveTV.LiveTvManager.RefreshEmbyChannelsInternal(IProgress`1 progress, CancellationToken cancellationToken)
Source: Emby.XmlTV
TargetSite: Void MoveNext()

I've attached the guide data exactly as returned from the IPTVEditor guide URL (it returns a gzip).

IPTVEditor_epg.xml (3).gzip

Posted

Hi, what url did you configure into the guide data provider? is it valid xml?

Valdorama
Posted

It's the URL provided by IPTVEditor:

image.png.85bbe591fa824763378c99c70905728c.png

It works in other applications (e.g. Channels DVR), and when I enter that URL in my browser, it downloads the gzip file (attached in the original post). The gzip does contain valid XML.

 

Posted
Just now, Valdorama said:

The gzip does contain valid XML.

 

How did you confirm that?

Valdorama
Posted

I opened up the gzip and extracted the xml file. The xml looks valid and Notepad++ confirms it.

Posted

How does notepad++ confirm it?

Valdorama
Posted

The 'Xml Tools' plug-in, and it's 'Check xml syntax' option.

Carlo
Posted

Was this a one-time error, or does it happen every time you refresh guide data?

Valdorama
Posted

It happens every time. I've looked in the XML file and can't see what the issue could be - the "<tv>" element (as referenced in the error message) is definitely closed properly. The line and position don't seem to point to anything obvious.

Valdorama
Posted

Looks like I may have sorted this. The guide URL can also be specified as https://opop.pro/xxxxyyyyzzzz/?xml=1 which streams the raw XML data, rather than the default (without the param) which delivers the data in gzip-compressed format. Presumably Emby was having issues processing the gzipped content. The guide is properly populated now.

  • Thanks 1

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...