Server Version#: 1.25.0.5246
Tuner Make/Model: HD HDHomeRun CONNECT QUATRO & HDHomeRun FLEX 4K
I was trying to add a second HDHome Run Tuner and am now stuck with “There was an unexpected error - Please visit our forums if you continue to experience problems”
oh sorry my mistake. I see a bunch of slow DB issues.
Can you shut down server. move the three tv.plex.providers.epg.cloud... database files someplace else for backup then restart server. You will need to re-add tuners and refresh EPG but any scheduled recordings should remain
they are located in the the Plex Media Server data folder /Plex Media Server/Plug-in Support/Databases/
Nov 17, 2021 00:34:29.313 [0x7f9c4a573b38] WARN - [E] web_service_t::get_device_status. Failed to make compound device for device uuid dvb#v4l#/sys/devices/pci0000:80/0000:80:02.2/0000:83:00.0/0000:84:01.0/0000:85:00.0:14f1:8880
Same version of Plex, also dockerized and same issue for me.
Added an xTeVe tuner just fine, but within a split second the guide had disappeared and the settings page of Live TV just throws an “unexpected error”
I’ve stopped xTeVe for now, so that hasn’t been running for a few days now.
I’ve tried:
Removing the tv.plex.providers.epg.xmltv… files in /Library/Application Support/Plex Media Server/Plug-in Support/Databases
Logging in via the servers local IP:32400
Incognito mode
Stopping/Starting the docker
Rebooting the server
Nothing really seems to work here…really strange that you can’t simply get to the page where you’re allowed to remove the DVR and create a new one.
I have solved my issue, although in an odd roundabout way.
I spun up another Plex server on another computer in docker. I added the tuners and was able to use that server without issue. While logged into the new server with it’s IP, I connected to my original server and was able to access the DVR config page! SO ODD!!!
I deleted all of the tuners from both servers, stopped the new one from running and connected to my original server and was able to access the DVR Live TV page again.
I have since set up the tuners, and all is working again as expected. Nuked the new plex server and removed it from authorized devices, and I am back in business.
Have no idea why this worked, I was just going to use the new server for Live TV and DVR until I was able to fix my original one, so this was all a happy accident.
Hopefully something here is useful to anyone and or the Plex developers. It’s over my head as to why I could control my old Plex install from a new one to fix an issue. MUST be something in the config of the old one. Anyway my issue is resolved.
I have looked at the logs and I am having difficulty matching the error screen you uploaded “There was an unexpected error” with the Plex Media Server log which was covering Nov 16, 2021 22:38 to 23:36
I can see successful requests to the server from Plex Web relating to the DVR with OTA Lineup “Local Broadcast Listings” - this was at 23:22:58 and cannot see any errors
This was for HDHomerun DVR on 192.168.10.22
Was the screenshot at 23:23 ? There are no errors in the server log at the time and also the requests from Plex Web all completed within few milliseconds - so not a slow response issue or timeout
These were the Plex Web requests which completed ok
Nov 16, 2021 23:22:58.096 [0x7f4908ccbb38] DEBUG - Request: [192.168.10.7:49280 (Allowed Network (Subnet))] GET /media/grabbers/devices/21/channels (21 live) GZIP Signed-in
Nov 16, 2021 23:22:58.096 [0x7f4908c62b38] DEBUG - Request: [192.168.10.7:49279 (Allowed Network (Subnet))] GET /livetv/epg/lineupchannels?lineup=lineup%3A%2F%2Ftv.plex.providers.epg.cloud%2F5fc76bcd2f220e002d6d5274%23Local%2520Broadcast%2520Listings%2520%252882%2520channels%2529&lineup=lineup%3A%2F%2Ftv.plex.providers.epg.cloud%2F5fc76b2a3f000e002d0c6f1d%23Local%2520Broadcast%2520Listings%2520%252884%2520channels%2529 (21 live) GZIP Signed-in
Nov 16, 2021 23:22:58.097 [0x7f4908c3fb38] DEBUG - Request: [192.168.10.7:49324 (Allowed Network (Subnet))] GET /tv.plex.providers.epg.cloud:18/lineups/dvr/channels (21 live) GZIP Signed-in
Nov 16, 2021 23:22:58.113 [0x7f4909053b38] DEBUG - Completed: [192.168.10.7:49280] 200 GET /media/grabbers/devices/21/channels (21 live) GZIP 17ms 1149 bytes (pipelined: 24)
Nov 16, 2021 23:22:58.294 [0x7f4909053b38] DEBUG - Completed: [192.168.10.7:49279] 200 GET /livetv/epg/lineupchannels?lineup=lineup%3A%2F%2Ftv.plex.providers.epg.cloud%2F5fc76bcd2f220e002d6d5274%23Local%2520Broadcast%2520Listings%2520%252882%2520channels%2529&lineup=lineup%3A%2F%2Ftv.plex.providers.epg.cloud%2F5fc76b2a3f000e002d0c6f1d%23Local%2520Broadcast%2520Listings%2520%252884%2520channels%2529 (21 live) GZIP 198ms 5178 bytes (pipelined: 24)
Nov 16, 2021 23:22:58.554 [0x7f4909030b38] DEBUG - Completed: [192.168.10.7:49324] 200 GET /tv.plex.providers.epg.cloud:18/lineups/dvr/channels (21 live) GZIP 456ms 350 bytes (pipelined: 12)
If problem persisted, I would then moved on to get Plex Web network logging using the browser dev console and saving a har file for all the requests and responses received by Plex Web
Also if there was some old invalid data held then I would have needed download of the Plex Media Server Database (through thr troubleshooting interface) to investigate further
The Plex Tuner Service logs show references to a PCI tuner identifying as “LG Electronics LGDT3306A” - Do you have a pci card ? Was there ever one ?
With regards to the HD Homerun - i am seeing different IP addresses
Which DVRs are on these IP Addresses
192.168.10.21 and 192.168.10.22
Nov 16, 2021 22:48:27.136 [0x7f4908403b38] DEBUG - NetworkServiceBrowser: found 1 SSDP devices via http://192.168.10.22:80/dms/device.xml
and
Nov 16, 2021 22:38:57.799 [0x7f4908403b38] DEBUG - NetworkServiceBrowser: found 1 SSDP devices via http://192.168.10.21:80/dms/device.xml
Nov 16, 2021 22:38:57.799 [0x7f4908403b38] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.10.21 (HDHomeRun DMS 10707A20)
Nov 16, 2021 22:49:07.541 [0x7f4908403b38] DEBUG - NetworkServiceBrowser: found 1 SSDP devices via http://192.168.10.21:80/atsc3/device.xml
Nov 16, 2021 22:49:07.541 [0x7f4908403b38] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.10.21 (HDHomeRun ATSC 10A13B14)
This log line is concerning - suggesting the Plex Media Server was seen on 192.168.10.21 before
Nov 16, 2021 22:48:27.115 [0x7f4908403b38] DEBUG - NetworkService: Replacing an old server at index 1 and address 192.168.10.21 (we just got packet from 192.168.10.22, index 1)
Do you use DHCP reservation ? Wondering if changing IP addresses has a bearing on some of the issues
“With regards to the HD Homerun - i am seeing different IP addresses
Which DVRs are on these IP Addresses
192.168.10.21 and 192.168.10.22”
I have two HDHome Runs. I had the newer 4K ATSC3.0/ATSC1.0 running on the system. I bought an older Quatro so I could use all 4 tuners, as it seems Plex does not yet support ATSC3.0 yet, as I was only able to use 2 of the 4 tuners.
Once I had the error, I did some experimenting, changing the IPs of the tuners, and removing them from the network completely to see if I would change the error message and access the configuration screen. Unfortunately none of that worked. I should of saved the logs before messing around with the system. I will definitely do that next time, as there are probably a few dead end errors caused by my troubleshooting attempts.
The whole thing started when I added the new (older) HDHome Run, set it up, then deleted the old (NEW) HDHomerun 4k. After deleting the 4K HR boom, error page… I wasn’t able to find the errors in the logs, so made the post.
“The Plex Tuner Service logs show references to a PCI tuner identifying as “LG Electronics LGDT3306A” - Do you have a pci card ? Was there ever one ?”
Yes, this is a Hauppauge WinTV-quadHD card. I was using it in the past, but was not set up in Plex at this time. It’s not currently in use at the moment, but am planning on setting it up again in the short future. The antenna moved in some of the high winds a while back, decided to get the 4k tuner before looking to see if it was supported, as TV usage in the house has gone up, decided to go external, as there is only so much room in the server.
I can confirm that spinning up another Plex instance, logging in and then going to Live TV & DVR works…I have been able to clear up the configuration now…sucky route, but I guess that’s the way it is…Plex support, where are you?
I tried this method, but without any success. May change IP of the HDHomeRun and try again, but wanted to add to this thread to see if support can chime in eventually
Added a 2nd HDHR, and it borked with the “unexpected error” message.
Completely non-functional LiveTV & DVR now. WTF?!
Surely folks “fixing” this by spinning up another Plex instance should give dev’s a clue where the issue is?! Hello?
Anyway - the above fix of commissioning another plex server was not enough for me - every time I accessed the DVR config page it was there for a second, then went back to the error.
Nothing would work so if you want to read what I needed to do - strap yourself in.
I had to power off my HDHR’s, then restart the original plex server, and while it was starting up and things were running “slowly” - I was able to quickly access the DVR config page from another plex client and click on “delete DVR” while it was starting.
15 minutes later and it still hadn’t “finished” deleting so I shut down the plex server again, removed the 3 files mentioned above by BigWheel: Plex Media Server/Plug-in Support/Databases/tv.plex.providers.epg.cloud- ....
I also recursively deleted: Plex Media Server/Plug-in Support/Caches/tv.plex.providers.epg.cloud-.....
I then started the original plex server again and it at least didn’t error and I could “finish” deleting the DVR config.
I then started the HDHR’s, and the DVR was happy to now add at least 1 of them for the time being. I added the 2nd one once the 1st one had finished it’s setup (including pulling in the guide data).
Anyway, all seems happy again for the time being. Hopefully this helps someone else until the devs can fix whatever is borked.
Yes, I used the IP but still got the error on the 2nd PMS.
Well, if everything works fine then you add another tuner (exact same make/model) which borks the entire config, then yeah there’s something weird going on for sure.
I guess the easiest solution, would be a “factory reset” button that would delete the DVR config files and everything associated with them to completely wipe out every part of it and set it to default. At least as a last result. It downloads the EPG every time you do anything anyway.
Unrelated but strange issue with my Hauppauge WinTV-quadHD card, it sees less channels with a channel scan than the HDHome Runs. Same antenna same cable, just moved it over to the HDHome Run. Worked fine before. I bought the card when live TV was announced, and worked fine. High winds moved the antenna, so deleted the DVR. Finally got back to it when I bought the ATSC3 tuner without checking if Plex supported it. No worries tho, as I can use it with other software while Plex uses the 1.0 tuners. Slick little boxes the HDHRuns! Was a long time MythTV user until Plex. Still like and miss some of MythTV’s features, easier to have everything in one place.
I just did this and it really did work. For the last command, it should be underscores, not -. - brought a syntax error. But I’m back to working. Hope this helps you too!
remove the db files from the original server tv.plex.providers.epg.cloud.... 3 files ending in .db, .db-shm, .db-wal /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-in Support/Databases
copy the 3 files from the new server to the original server (from the config dir then same file path)
start the original server again
delete the dvr
set up the dvr fresh
delete the docker container and all the directories