Can't add setup Plex DVR and download EPG - I see two errors: Unable to load channel mappings and Unable to fetch guide settings

Server Version#: 1.19.4.2935
Player Version#:
Tuner Make/Model: HDHomeRun Quattro
Guide/Lineup name: Freeview National Lineup
Using XMLTV?: No
Channel number/Name:

I recently had problems with the EPG missing data - it would only say - Channel programming, so I deleted the DVR and have been trying to re-add it, however it fails.

PMS finds my HDHomeRun CONNECT QUATRO and selecting recognises the 193 channels it has access to.

When I enter my postcode to search for the best EPG - I see the error; ‘Unable to fetch Guide settings’ or the Continue button remains unselectable (greyed out) until I stop and restart the PMS service.

When DVR Setup starts to download the guide, it gets to 100% and recognises the guide ‘Freeview Granada OTA Broa----’ (although I’ve seen it pick up the Freeview National Lineup in previous attempts – as per title) and starts Loading channel mappings but finishes with ‘Unable to load channel mappings’, choosing Continue results in the error: ‘There was a problem saving your DVR’.

I can confirm that the HDHomeRun Quatro is working and can access the HDHR5-4DT channels from other devices, e.g. TVs and can access the HDHR website to check the system status, it is upto date with firmware version – 20200521 and its model number is 1252329F.

My internet connection is a three.co.uk mobile broadband router with sufficient download speed and until maybe a week ago, has worked very well in supporting EPG download as well as remote access, I don’t believe my mobile broadband is a problem, unless something has changed within the service.

I have attached the zipfile of my server logs in non-verbose mode and would like to add that I’ve tried it with the UK xmltv feed, however I also go the error – ‘Unable to fetch guide settings’.

Plex Media Server Logs_2020-06-16_21-01-51.zip (476.5 KB)

Some extra information; I have fully deleted the PMS and reinstalled it several times, including removing the registry settings and have also removed the local user data files per;

Finally, my main PMS box is a ThinkCentre Ryzen5 PRO 3400 with 20GB RAM but I have also tried installing the DVR on an older PC - intel i7 3770 with 16GB RAM, it also fails to download the EPG and fails to add the DVR.

First of all a number of users have reported issues with three network and DVR setup with errors to reach our service at https://epg.provider.plex.tv
and I can see similar problems in your log

Out of 32 requests to the service only 6 completed successfully with the rest timing out and that would explain why sometimes you saw the National lineup instead of Granada lineup - as probably the request for the granada ota lineup channels timedout but the national one did not

There is nothing i can help with until you get this ISP issue resolved

See forum topic from another user with Three broadband

Thank you for responding, in my checks before logging the problem, I did try using my phone as a tethered provider, my phone is on the EE.co.uk service in the UK butI had the same problem, so wasn’t convinced it was three.co.uk, but I will retry and feedback.

However there was something I noticed in the server logs that didn’t make sense;

Jun 16, 2020 21:01:12.102 [3720] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.0.254:49152/wps_device.xml
Jun 16, 2020 21:01:12.102 [3720] DEBUG - HTTP requesting GET http://192.168.0.254:49152/wps_device.xml
Jun 16, 2020 21:01:27.109 [3720] ERROR - Error issuing curl_easy_perform(handle): 28
Jun 16, 2020 21:01:27.109 [3720] ERROR - SSDP: Error parsing device schema for http://192.168.0.254:49152/wps_device.xml

192.168.0.254 does not exist, it did previously and was a Sky extender for my previous internet provider, however I moved to mobile broadband in March and moved my network to 192.168.1.x so as to use the default network settings on my router - am unsure why the PMS was looking for 192.168.0.254 when it knows the network is 192.168.0.x?

As an addendum, I’ve rerun the setup this morning and looked at todays equivalent logs, it’s no longer erroring on 192.168.0.254, it’s now trying to run the same commands on 192.168.1.5 - I haven’t any devices with that IP address but am seeing a repeat of the previous error, see below from today’s logs, can I ask where PMS is getting these unused IP addresses from?:

Jun 19, 2020 10:59:18.598 [14928] ERROR - Error issuing curl_easy_perform(handle): 28
Jun 19, 2020 10:59:18.598 [14928] DEBUG - HTTP simulating 408 after curl timeout
Jun 19, 2020 10:59:18.598 [14928] ERROR - SSDP: Error parsing device schema for http://192.168.1.5:49153/wps_device.xml

I’ll try my EE network but do the above errors mean anything?

best regards

would need logs for that to see what the issue was

These should be harmless. We send out SSDP Search periodically and then devices on the local network respond with details of what urls to use to get more info / control the device etc… I have come across devices giving false url’s

The only way to find out is to run wireshark and start capture of network traffic and when you know you have covered the times in the log where these appear then stop the capture and save the pcap file - you can have a look it yourself or send me zipped pcap with associated Plex Media Server logs

You were right - it was my mobile network provider, unsure why tethering didn’t fail previously but swapping my router sim over to my EE sim resulted in it working immediately, so I need to look at changing my mobile broadband provider unless you can suggest any local changes that I can use as a work-around?

Assuming not, thanks for the prompt responses.

I thought I’d update this thread with a solution I’ve found.

Using a VPN to connect to a different country for the EPG download seems to resolve the problem, I’m able to get a full EPG download by VPN’ing via a US server.

Hope that helps others experiencing the same problem?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.