[Kodi 17 Krypton] DVBViewer not working 17.1 -- cannot reach server
#1
I just upgraded from Kodi 16 to 17.1 and Live TV isn't working anymore: I am getting an error message in Kodi saying the PVR addon cannot reach the DVB service. I didn't change any configuration; it still says 127.0.0.1 and port 8089 in the addon settings. I can reach 127.0.0.1:8089 using a web browser.

In kodi.log (see: https://pastebin.com/PMx9tWr5) I can see the DVBViewer addon is receiving a 404 (which I am also receiving when trying to manually open http://127.0.0.1:8089/api/status2.html in a browser):
Code:
01:38:24.032 T:2808    INFO: AddOnLog: DVBViewer Client: Trying to connect to the backend service...
01:38:24.033 T:2808   DEBUG: CurlFile::Open(0DB1ECB0) http://127.0.0.1:8089/api/version.html
01:38:24.033 T:2808   DEBUG: Curl::Debug - TEXT: timeout on name lookup is not supported
01:38:24.033 T:2808   DEBUG: Curl::Debug - TEXT: Hostname 127.0.0.1 was found in DNS cache
01:38:24.033 T:2808   DEBUG: Curl::Debug - TEXT:   Trying 127.0.0.1...
01:38:24.034 T:2808   DEBUG: Curl::Debug - TEXT: Connected to 127.0.0.1 (127.0.0.1) port 8089 (#34)
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: GET /api/version.html HTTP/1.1
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: Host: 127.0.0.1:8089
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: Range: bytes=0-
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: User-Agent: Kodi/17.1 (Windows NT 6.1; WOW64) App_Bitness/32 Version/17.1-Git:20170320-fc1619b
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: Accept: */*
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: Accept-Charset: UTF-8,*;q=0.8
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_IN: HTTP/1.1 200 OK
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_IN: Content-Type: text/xml; charset=UTF-8
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_IN: Content-Length: 124
01:38:24.034 T:2808   DEBUG: Curl::Debug - TEXT: Connection #34 to host 127.0.0.1 left intact
01:38:24.034 T:2808  NOTICE: AddOnLog: DVBViewer Client: Checking backend version...
01:38:24.034 T:2808  NOTICE: AddOnLog: DVBViewer Client: Version: 18743552
01:38:24.034 T:2808   DEBUG: CurlFile::Open(0DB1ECB0) http://127.0.0.1:8089/api/status2.html
01:38:24.034 T:2808   DEBUG: Curl::Debug - TEXT: Found bundle for host 127.0.0.1: 0x6a82ca8 [can pipeline]
01:38:24.034 T:2808   DEBUG: Curl::Debug - TEXT: Re-using existing connection! (#34) with host 127.0.0.1
01:38:24.034 T:2808   DEBUG: Curl::Debug - TEXT: Connected to 127.0.0.1 (127.0.0.1) port 8089 (#34)
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: GET /api/status2.html HTTP/1.1
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: Host: 127.0.0.1:8089
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: Range: bytes=0-
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: User-Agent: Kodi/17.1 (Windows NT 6.1; WOW64) App_Bitness/32 Version/17.1-Git:20170320-fc1619b
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: Accept: */*
01:38:24.034 T:2808   DEBUG: Curl::Debug - HEADER_OUT: Accept-Charset: UTF-8,*;q=0.8
01:38:24.035 T:2808   DEBUG: Curl::Debug - TEXT: The requested URL returned error: 404 Not Found
01:38:24.035 T:2808   DEBUG: Curl::Debug - TEXT: Closing connection 34
01:38:24.035 T:2808   ERROR: CCurlFile::Open failed with code 404 for http://127.0.0.1:8089/api/status2.html
01:38:24.035 T:2808    INFO: AddOnLog: DVBViewer Client: Connection to the backend service failed. Retrying in 10 seconds...

I am using a clean userprofile (only changed the skin to Experience1080, nothing else).
Reply
#2
You need to upgrade the recording service to 1.31 or above.
Reply
#3
Yah, I just figured it myself that it might be due to an old version. Cost me another half hour to realize that recording service is not part of the main application (so downloading the latest DVBViewer wouldn't change anything) AND it's hidden somewhere at the very bottom of the download page of DVBViewer's customer area. Super confusing.

Thanks anyway. Should work now I hope.
Reply
#4
jaochoo: its because they want the money for they new product "media server" which is nearly the same as the recording service.
Reply
#5
you can stick to "old" recording service...it has been free...it will be kept free..

only the "new" media server needs an upgrade licens...

however...if you have a running/working system there is no need to upgrade to media server (ok i did at both of my servers)
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
DVBViewer not working 17.1 -- cannot reach server00