"There was a problem saving your DVR."

Live TV & DVR
1

Server Version#: 1.19.4.2902
Player Version#: Web 4.35.1
Tuner Make/Model: xTeVe
Guide/Lineup name: N/A
Using XMLTV?: Yes
Channel number/Name: ALL

Been having an issue trying to add my DVR tuner to Plex. Always getting the “…problem saving your DVR” message after adding manual XMLTV data. I’ve attached the logs as follows. Any and all help would be greatly appreciated! Plex Media Server.log (7.5 MB)

2

Would you be able to zip up (compress) all of your Plex Media Server logs, and post it here please.

3

Thank you so much for the response. Here are the logs.Plex Media Server Logs_2020-06-10_16-03-40.zip (7.7 MB)

4

Thanks for the initial log and subsequent zip of the logs

I can only see one setup for the DVR in the logs - at 01:30 am on the 4th of June - your initial log file.

For the latest logs - all i can see are dead DVRs - either because they are unreachable or you are using host names for them and not setup in the DNS and there are different DVRs assigned same host name

Lets go back to the setup that you say failed to save on the 4th June

The server log does not show any errors being returned to Plex Web during the setup and there is also no evidence of any delayed response leading to a timeout

There were a sequence of actions for the setup and they all appear to have succeeded as far as the Plex Media Server was concerned

Jun 04, 2020 01:30:37.245 [0x7f741dffb700] DEBUG - Request: [172.18.0.5:50882 (WAN)] GET /livetv/epg/languages (25 live) GZIP Signed-in Token (MANASTORY)
Jun 04, 2020 01:30:37.245 [0x7f74ffca2700] DEBUG - Completed: [172.18.0.5:50882] 200 GET /livetv/epg/languages (25 live) GZIP 0ms 3812 bytes

Jun 04, 2020 01:30:45.106 [0x7f739b7fe700] DEBUG - Request: [172.18.0.5:50940 (WAN)] GET /livetv/epg/channels?lineup=lineup%3A%2F%2Ftv.plex.providers.epg.xmltv%2Fxteve%2Fxteve.xml%23My%2520Guide (25 live) GZIP Signed-in Token (MANASTORY)
Jun 04, 2020 01:30:45.153 [0x7f74ffca2700] DEBUG - Completed: [172.18.0.5:50940] 200 GET /livetv/epg/channels?lineup=lineup%3A%2F%2Ftv.plex.providers.epg.xmltv%2Fxteve%2Fxteve.xml%23My%2520Guide (25 live) GZIP 46ms 5653 bytes

Jun 04, 2020 01:30:45.167 [0x7f74ae7fc700] DEBUG - Request: [172.18.0.5:50942 (WAN)] GET /livetv/epg/channelmap?device=device%3A%2F%2Ftv.plex.grabbers.hdhomerun%2F2020-05-AQFE-R1RF81&lineup=lineup%3A%2F%2Ftv.plex.providers.epg.xmltv%2Fxteve%2Fxteve.xml%23My%2520Guide (25 live) GZIP Signed-in Token (MANASTORY)
Jun 04, 2020 01:30:45.261 [0x7f74ffca2700] DEBUG - Completed: [172.18.0.5:50942] 200 GET /livetv/epg/channelmap?device=device%3A%2F%2Ftv.plex.grabbers.hdhomerun%2F2020-05-AQFE-R1RF81&lineup=lineup%3A%2F%2Ftv.plex.providers.epg.xmltv%2Fxteve%2Fxteve.xml%23My%2520Guide (25 live) GZIP 94ms 2056 bytes

Jun 04, 2020 01:30:46.629 [0x7f741f7fe700] DEBUG - Request: [172.18.0.5:50974 (WAN)] PUT /media/grabbers/devices/16?enabled=1 (24 live) GZIP Signed-in Token (MANASTORY)
Jun 04, 2020 01:30:46.630 [0x7f74ffca2700] DEBUG - Completed: [172.18.0.5:50974] 200 PUT /media/grabbers/devices/16?enabled=1 (24 live) GZIP 0ms 467 bytes

So if you did get an error message displayed by Plex Web at this time - i would need to see both the Plex App log as well as a corresponding server log.

The responses to Plex Web for the DVR setup were all HTTP Response code 200 which indicate success.

The above implies it was saved. So would really need screenshots and Plex Web logs as well as server logs. I will detail this in my response.

I do not know if the use of host names is contributing to the issue - you could remove all your non standard configuration and just use the hdhomerun IP addresses and see if that makes a difference

The hdhomerun device you were setting up appears to have been this one
2020-05-AQFE-R1RF81

You seem to have two DVRs with the ip address 172.18.0.8 - one on port 6077 and one on port 34400.

Jun 10, 2020 08:21:21.603 [0x7f3c827fc700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/12345678 at http://172.18.0.8:6077
Jun 10, 2020 08:21:21.603 [0x7f3c827fc700] DEBUG - HTTP requesting GET http://172.18.0.8:6077/discover.json
Jun 10, 2020 08:21:24.670 [0x7f3c827fc700] WARN - HTTP error requesting GET http://172.18.0.8:6077/discover.json (7, Couldn't connect to server) (Failed to connect to 172.18.0.8 port 6077: No route to host)

Jun 10, 2020 08:21:24.742 [0x7f3c827fc700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/2020-05-AQFE-R1RF81 at http://172.18.0.8:34400
Jun 10, 2020 08:21:24.742 [0x7f3c827fc700] DEBUG - HTTP requesting GET http://172.18.0.8:34400/discover.json
Jun 10, 2020 08:21:27.742 [0x7f3c827fc700] WARN - HTTP error requesting GET http://172.18.0.8:34400/discover.json (7, Couldn't connect to server) (Failed to connect to 172.18.0.8 port 34400: No route to host)

And this morning - all appeared dead for one reason or another

DVR 12345678 at http://172.18.0.8:6077 (No route to host)

Jun 10, 2020 08:21:21.603 [0x7f3c827fc700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/12345678 at http://172.18.0.8:6077
Jun 10, 2020 08:21:21.603 [0x7f3c827fc700] DEBUG - HTTP requesting GET http://172.18.0.8:6077/discover.json
Jun 10, 2020 08:21:24.670 [0x7f3c827fc700] ERROR - Error issuing curl_easy_perform(handle): 7
Jun 10, 2020 08:21:24.670 [0x7f3c827fc700] WARN - HTTP error requesting GET http://172.18.0.8:6077/discover.json (7, Couldn't connect to server) (Failed to connect to 172.18.0.8 port 6077: No route to host)
Jun 10, 2020 08:21:24.671 [0x7f3c827fc700] ERROR - DVR:Device: Error refreshing existing device device://tv.plex.grabbers.hdhomerun/12345678, marking as dead.

DVR 2019-08-EVV3-FHR7UN at http://filearchy.synology.me:34400 (Could not resolve host)

Jun 10, 2020 08:21:24.671 [0x7f3c827fc700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/2019-08-EVV3-FHR7UN at http://filearchy.synology.me:34400
Jun 10, 2020 08:21:24.671 [0x7f3c827fc700] DEBUG - HTTP requesting GET http://filearchy.synology.me:34400/discover.json
Jun 10, 2020 08:21:24.714 [0x7f3c827fc700] ERROR - Error issuing curl_easy_perform(handle): 6
Jun 10, 2020 08:21:24.714 [0x7f3c827fc700] WARN - HTTP error requesting GET http://filearchy.synology.me:34400/discover.json (6, Couldn't resolve host name) (Could not resolve host: filearchy.synology.me)
Jun 10, 2020 08:21:24.716 [0x7f3c827fc700] ERROR - DVR:Device: Error refreshing existing device device://tv.plex.grabbers.hdhomerun/2019-08-EVV3-FHR7UN, marking as dead.

DVR 2020-03-MNPA-8NDYB5 at http://xteve.manastory.tv (HTTP 503 response)

Jun 10, 2020 08:21:24.716 [0x7f3c827fc700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/2020-03-MNPA-8NDYB5 at http://xteve.manastory.tv
Jun 10, 2020 08:21:24.717 [0x7f3c827fc700] DEBUG - HTTP requesting GET http://xteve.manastory.tv/discover.json
Jun 10, 2020 08:21:24.738 [0x7f3c827fc700] DEBUG - HTTP 503 response from GET http://xteve.manastory.tv/discover.json
Jun 10, 2020 08:21:24.738 [0x7f3c827fc700] DEBUG - JSON parse error: Invalid value. (0)
Jun 10, 2020 08:21:24.739 [0x7f3c827fc700] ERROR - DVR:Device: Error refreshing existing device device://tv.plex.grabbers.hdhomerun/2020-03-MNPA-8NDYB5, marking as dead.

DVR 2020-05-AQFE-R1QOU8 at http://xteve.manastory.tv (HTTP 503 response)

Jun 10, 2020 08:21:24.739 [0x7f3c827fc700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/2020-05-AQFE-R1QOU8 at http://xteve.manastory.tv
Jun 10, 2020 08:21:24.740 [0x7f3c827fc700] DEBUG - HTTP requesting GET http://xteve.manastory.tv/discover.json
Jun 10, 2020 08:21:24.740 [0x7f3c827fc700] DEBUG - HTTP 503 response from GET http://xteve.manastory.tv/discover.json
Jun 10, 2020 08:21:24.741 [0x7f3c827fc700] DEBUG - JSON parse error: Invalid value. (0)
Jun 10, 2020 08:21:24.742 [0x7f3c827fc700] ERROR - DVR:Device: Error refreshing existing device device://tv.plex.grabbers.hdhomerun/2020-05-AQFE-R1QOU8, marking as dead.

DVR 2020-05-AQFE-R1RF81 at http://172.18.0.8:34400 (No route to host)

Jun 10, 2020 08:21:24.742 [0x7f3c827fc700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/2020-05-AQFE-R1RF81 at http://172.18.0.8:34400
Jun 10, 2020 08:21:24.742 [0x7f3c827fc700] DEBUG - HTTP requesting GET http://172.18.0.8:34400/discover.json
Jun 10, 2020 08:21:27.742 [0x7f3c827fc700] ERROR - Error issuing curl_easy_perform(handle): 7
Jun 10, 2020 08:21:27.742 [0x7f3c827fc700] WARN - HTTP error requesting GET http://172.18.0.8:34400/discover.json (7, Couldn't connect to server) (Failed to connect to 172.18.0.8 port 34400: No route to host)
Jun 10, 2020 08:21:27.743 [0x7f3c827fc700] ERROR - DVR:Device: Error refreshing existing device device://tv.plex.grabbers.hdhomerun/2020-05-AQFE-R1RF81, marking as dead.

Could you simplify your setup and and assign static / dhcp reserved IP addresses to the DVRs and make sure no different DVRs have same IP address and no host names used.

With a standard setup and after you know the DVR is reachable through the HD Homerun setup app and is free and not in use, then go through the setup.

So is the DVR not showing at the moment when you go through DVR Settings?

To understand the failure, need to enable plex web logging and also browser dev console logs - through F12 and console / preserve log and then at the end save as har file as well as getting the plex web log and screenshot of the error and time it arose.

To enable plex web logging, click on “settings” icon (top right) and then click “Show Advanced” button and in left sidebar go to “Plex Web” set and click on “Debug” - set Log level to be “verbose” and save changes.

Then setup browser dev console logging and ensure preserve log is ticked and reproduce the problem

When the error arises, take a screenshot with the time of the error showing
Go to settings again with Show Advanced and in Plex Web set click on debug and click on “here” where it says “You can view the debug logs here” and select all and copy and save in a text file

Then save the console and network log in the browser

and download the server logs

Send me the browser network / console log by private message as it would have tokens and also include the plex web log and you can attach server logs here

Curious about the network setup. Are you managing this remotely ? Requests seem to be from within the local network but are actually forwarded from a WAN IP address on 92.40.xxx.xxx

and i have an unrelated question - i noticed some null photos url’s in the log !
At the time you were adding posters for “Wild Style” and at some point the client app (was it plex web) got a null for the url

Jun 10, 2020 12:39:47.269 [0x7f3b9d7fa700] DEBUG - Request: [172.18.0.4:42986 (WAN)] GET /photo/:/transcode?width=1490&height=1490&upscale=1&url=null (17 live) GZIP Signed-in Token (MANASTORY)

Interested to know how that arose and if it was through Plex Web and from which screens - you can PM on this

5

@mana195 Thanks for the plex web and browser console logs and associated responses

I can see the following errors in the console log

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at [https://plex.manastory.tv/media/grabbers/devices/3/channelmap?channelsEnabled=1000%2C1001%2C1002%2C1003%2C1004%2C1005%2C1006%2C1007%2C1008%2C1009%2C1010](https://plex.manastory.tv/media/grabbers/devices/3/channelmap?channelsEnabled=1000%2C1001%2C1002%2C1003%2C1004%2C1005%2C1006%2C1007%2C1008%2C1009%2C1010%2C1011%2C1012%2C1013%2C1014%2C1015%2C1016%2C1017%2C1018%2C1019%2C1020%2C1021%2C1022%2C1023%2C1024%2C1025%2C1026%2C1027%2C1028%2C1029%2C1030%2C1031%2C1032%2C1033%2C1034%2C1035%2C1036%2C1037%2C1038%2C1039%2C1040%2C1041%2C1042%2C1043%2C1044%2C1045%2C1046%2C1047%2C1048%2C1049%2C1050%2C1051%2C1052%2C1053%2C1054%2C1055%2C1056%2C1057%2C1058%2C1059%2C1060%2C1061%2C1062%2C1063%2C1064%2C1065%2C1066%2C1067%2C1068%2C1069%2C1070%2C1071%2C1072%2C1073%2C1074%2C1075%2C1076%2C1077%2C1078%2C1079%2C1080%2C1081%2C1082%2C1083%2C1084%2C1085%2C1086%2C1087%2C1088%2C1089%2C1090%2C1091%2C1092%2C1093%2C1094%2C1095%2C1096%2C1097%2C1098%2C1099%2C1100%2C1101%2C1102%2C1103%2C1104%2C1105%2C1106%2C1107%2C1108%2C1109%2C1110%2C1111%2C1112%2C1113%2C1114%2C1115%2C1116%2C1117%2C11)

I suspect it relates to using domain names and some security checks within the browser

Could you go through setup without domain names being in use and see if the problem goes away.

6

@mana195

I have referred this to the Web Desktop team to see if the block for the request is expected

I suspect if you avoid using a WAN connection to the server (the requests to your server custom access url were forwarded from a 92.40.xxx.xxx address whilst appearing as coming from within the local network 172.18.0.3 - I presume this is a proxy server.

So try to go through DVR Setup directly on the server through http://127.0.0.1:32400/web or http://172.18.0.12:32400/web and see if that gets round the problem

7

@mana195
Apologies for the multiple posts - there are two specific aspects here and we need to identify which is causing the problem

  • use of domain and Custom Server Access url
  • Having a proxy server on 172.18.0.3

I am inclined now to think that it is the proxy server that is leading to this block - so try disabling that first

8

Ah, I see. My server is remote so I’ll have to figure out the best way to do this since I can’t do it locally. I’ll try through SSH access now and report back here.

Thank you so much for your help!

9

It might be just a matter of getting rid of the proxy server. You should be able to access a remote server without having a proxy server in the way

10

I had a similar issue and this helped pin point me to the issue, I imagine that the proxy server is nginx. You can advert this issue by creating a file in: /etc/nginx/vhost.d/{VIRTUAL_HOST}_location or where this is located on this system & add this in. {VIRTUAL_HOST} is your plex virtual host

     if ($request_method = 'OPTIONS') {
        add_header 'Access-Control-Allow-Origin' '*';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
        #
        # Custom headers and headers various browsers *should* be OK with but aren't
        #
        add_header 'Access-Control-Allow-Headers' 'DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range';
        #
        # Tell client that this pre-flight info is valid for 20 days
        #
        add_header 'Access-Control-Max-Age' 1728000;
        add_header 'Content-Type' 'text/plain; charset=utf-8';
        add_header 'Content-Length' 0;
        return 204;
     }
     if ($request_method = 'POST') {
        add_header 'Access-Control-Allow-Origin' '*';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
        add_header 'Access-Control-Allow-Headers' 'DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range';
        add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range';
     }
     if ($request_method = 'GET') {
        add_header 'Access-Control-Allow-Origin' '*';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
        add_header 'Access-Control-Allow-Headers' 'DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range';
        add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range';
     }
11

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