Server Version#:
Player Version#:
Latest versions on Qnap nas.
problem
epg guide not loading any listings. also plex now giving me for hd homerun tuner a wan address instead of my local 192. address
any ideas?
Also have no program guide at all on my WD PR2100. I rescanned channels, it spun it’s wheels saying it was downloading lots of data, but then it shows nothing in the program guide
There was an issue giving rise to JSON Parse Error where the response for the guide refresh contained error 403 Forbidden. This should be fixed now.
Additionally Plex Media Server beta 1.14.0.5465 has retries for failed requests to fetch the guide - so that in itself would have helped whilst the issue was there
Please do manual update to the guide and once that completes ok, then incremental updates would ensure the guide remains up to date
If problems persist, please provide fresh logs from the server with debug logging enabled beforehand and also a zip of the Diagnostics directory which is within the Plex Media Server data area
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
https://support.plex.tv/articles/202915258-where-is-the-plex-media-server-data-directory-located/
I’m on version 1.13.9.5456 (on PR2100) - production build. Plex was ok for me the past two days, but today I had to refresh the guide twice and do another Plex restart before it would load the guide. You’re saying the fix is in the beta version now, and I can just wait for the next production build?
may be the problem has come back ? or a different issue
Can you upload the zipped logs and a zip of the Diagnostics directory as mentioned in my post
I did not say that. I said that the beta has a retry for any failed request to refresh and this retry may help circumventing the failures. Our understanding is that the failures seen before which lead to a JSON Parse Error logged and a diagnsotic JSON file save in the directory has been resolved by our guide metadata provider. If this is not the case, i would like to know and the logs and directory zip would help with that
Ok, I’ve got the two zip files, but I don’t see how to attach them. Maybe I’m a little dense this morning (not the first time)…
EDIT: Never mind. I finally see it 
plex_diagbkp.tar.gz (2.4 KB)
Plex Media Server Logs_2018-11-15_10-52-57.zip (4.5 MB)
I am new user running Plex version 1.13.9.5456 on an Nvidia Shield TV with a dual tuner Hauppage tuner and have been and continue to experience all the EPG symptoms described here. I have been doing the 20 try refresh each morning to get my guide updated. Here is the thing: I have disabled automatic Guide refresh in my server settings (only thing enabled is optimize database, remove old bundles and remove cache.) However each morning when I check my guide it is damaged – one channel (ABC) is missing almost all of its data. The rest of the guide is fine. I fix this by doing the manual refresh – which still takes multiple retries even as of this morning. Note: though I have only had debug logging on for a few days I haven’t seen the JSON message in my log though I could be looking in the wrong log file). Anyway, if you look at my log file(s) from today (uploaded) you will see the server seems to have run a guide refresh at 4am and maybe scheduled another for sometime after 8am? I ran my manual refresh a little after 7am. Besides the obvious question of why is only one of my channels EPG data getting lost/damaged, why doesn’t disabling automatic EPG refresh actually disable it? I can live with the current EPG problem if I can avoid it by disabling the EPG refresh and doing a manual update every week or so, but having to refresh everyday is kind of a pain. By the way, as a newbie, what do you mean by the Diagnostics directory as there isn’t one on my server? Is there another setting I need to enable? Logs.zip (2.4 MB)
Thank you very much. The problem has come back. The frequency reduced to only 1 failure on 13th and 14th but today you had 2 failures at 09:39 PMS time and 09:48.
Will refer it back to our metdata provider
Running with beta 1.14.0.5465 may help as the failed request would get retried (But i need to tell you there is one issue with the beta - uPnP port mapping for remote access may fail on some routers) - a fix will get released
Thanks much
Well, this is interesting. When I went to look at my Plex schedule, it seemed fine, so I restarted Plex as usual (I restart it every day between recordings). But when I looked at the schedule afterwards, all kinds of upcoming recordings were missing (not scheduled) anymore. (I’m not talking about ALL upcoming recordings, just some that spanned the time from 10am to 8pm - see attached…) I updated the program guide (no error this time?) but the recordings didn’t reappear in the schedule. Nevertheless, Plex started recording a movie that started at 10am (and when I look at the main program guide, it shows the movie being recorded). So, I’m not sure what’s going on here. The program guide is ok, but the recording schedule is not being drawn correctly? Wrong time zone in the recording schedule? As soon as I get a break in recording, I’ll generate those 2 zip files and post them again…
Well tonights recording were not on my list but all the others were for the rest of the week, I added a new record for them, still didn’t fix it, I removed some channels id never watch from hd home run tuner, then went to plex and did a channel scan to drop the channels and of course it did a guidel search. After the search tonight s and all the others to be recorded were now there.
Hmm, sounds like a plan. I’ll try that when I get a break in activity. Thanks
Edit: I won’t post more logs unless I see the same problem tomorrow. Frankly, I’m not sure if doing the above fixed the problem or not. I’ll have to check the schedule before I restart Plex tomorrow…
Further to my earlier notes here and here, the issue should now be fixed.
It was initially fixed on the 14th November but there were few reported errors coming back on the 15th. The errors are no longer being returned by our Guide metadata provider
If you do have gaps or To Be Announced within the 2-week guide data, please do a manual full refresh. The automatic incremental updates which happen every 4 hours would look after the next 12 hours or so and also extending the end to ensure there is 14 days of guide data
