Thanks for the feedback. There is no evidence in the log extract you posted of any EPG database issue - so I am not sure why removing the EPG database resolved the issue.
The log extract just shows Plex Web asking the Plex Media Server for DVR device list / info and this list was returned to Plex Web - I cannot tell what xml was returned to Plex Web and if the problem repeats itself - we can replicate the Plex Web request in curl in windows command line and see what gets returned
I would need also screenshots from Plex Web with time shown so I can relate it to log entries in the Plex Media Server log - also of course it is always beneficial to have full server logs zip - in case there were logged issues earlier on
If the issue arises again - then after you take the Plex Web screenshots and noting down the exact times, start a windows command line session and type this command
curl -X POST -o "%LocalAppData%\dvr-devices_yyyymmdd_hhmm.xml" http://127.0.0.1:32400/media/grabbers/devices/discover?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxxxx
substitute date/time for yyyymmdd_hhmm in the output filename and instead of xxxxxxxxxx put in the server security token - see this support article for how to find the token string
Zip the output file “%LocalAppData%\dvr-devices_yyyymmdd_hhmm.xml” and send me privately - Please note down how long the curl command takes to complete
This together with zipped server logs and Plex Web screenshots showing the problem
Update:
It would be useful to also capture the responses for these requests and add these to the diagnostics
http://192.168.0.35:80/discover.json
http://192.168.0.35:80/lineup_status.json
