Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 40

Thread: New NextPVR client for Raspberry Pi 2 and 3.

  1. #21
    Join Date
    Aug 2005
    Location
    Houston
    Posts
    4,796
    i'm having trouble installing using 'lite' raspbian...says 'dependancies problems prevent configuration of nextpivr:
    nextpivr depends on omxplayer however it is not installed..

    it lists omxplayer, lirc, python-lirc, and libcec3 as not installed.

    Aha!! Seems like you have to do sudo apt-get -f install to get dependancies BEFORE you do dpkg line...
    Last edited by pBS; 2017-04-19 at 05:43 AM.
    Hardware: HDHR Prime, HDPVR 1212, Raspberry pi2, VFD display w/LCDSmartie

  2. #22
    Join Date
    Aug 2005
    Location
    Houston
    Posts
    4,796
    now it has installed fine, but when i click server, i just get black screen...after i hit end, it pops back to ip screen...
    any ideas?
    Last edited by pBS; 2017-04-19 at 01:35 AM.
    Hardware: HDHR Prime, HDPVR 1212, Raspberry pi2, VFD display w/LCDSmartie

  3. #23
    Join Date
    Aug 2005
    Location
    Houston
    Posts
    4,796
    hmmm,seems i have to do dpkg line, then apt-get -f install, then dpkg line again for it to not have problems with dependancies...?
    still just black screen after hitting my server ip.
    formatted another card and tried twice, same exact results..[on an RPI2]

    hmm,maybe a newa problem? it wasn't working for browser.
    i re-setup newa from scratch, now working in browser... still same black screen and forbidden in log..

    web.log from server:
    Code:
    [...startup]
    2017-04-18 21:13:53.854	[DEBUG][19]	Starting webserver for IPv6/IPv4
    2017-04-18 21:13:54.505	[INFO][16]	About to connect to remote recording service
    2017-04-18 21:13:54.533	[DEBUG][16]	RecordingServiceProxy@exit
    2017-04-18 21:13:54.534	[DEBUG][16]	Got Web Request (::ffff:192.123.1.129): /control    key=-1&size=960x540&client=sdl.RPI3.940b8:27:eb:4c:95:74&quality=high&sid=792cef595d1b4a6aa58dc3ec9a9eb278
    2017-04-18 21:13:54.545	[DEBUG][16]	403 Forbidden
    2017-04-18 21:13:54.572	[DEBUG][19]	Got Web Request (::ffff:192.123.1.129): /activity    format=json&client=sdl.RPI3.940b8:27:eb:4c:95:74&time=1453566159131&sid=792cef595d1b4a6aa58dc3ec9a9eb278
    2017-04-18 21:13:54.575	[DEBUG][19]	403 Forbidden
    2017-04-18 21:14:01.485	[DEBUG][17]	Got Web Request (::ffff:192.123.1.129): /control    key=-1&size=960x540&client=sdl.RPI3.940b8:27:eb:4c:95:74&quality=high&sid=792cef595d1b4a6aa58dc3ec9a9eb278
    2017-04-18 21:14:01.485	[DEBUG][17]	403 Forbidden
    2017-04-18 21:14:01.510	[DEBUG][19]	Got Web Request (::ffff:192.123.1.129): /activity    format=json&client=sdl.RPI3.940b8:27:eb:4c:95:74&time=1453566159131&sid=792cef595d1b4a6aa58dc3ec9a9eb278
    2017-04-18 21:14:01.511	[DEBUG][19]	403 Forbidden
    Last edited by pBS; 2017-04-19 at 03:33 AM.
    Hardware: HDHR Prime, HDPVR 1212, Raspberry pi2, VFD display w/LCDSmartie

  4. #24
    Join Date
    Jul 2006
    Location
    Sweden
    Posts
    453
    Quote Originally Posted by pBS View Post
    i'm having trouble installing using 'lite' raspbian...says 'dependancies problems prevent configuration of nextpivr:
    nextpivr depends on omxplayer however it is not installed..

    it lists omxplayer, lirc, python-lirc, and libcec3 as not installed.
    Quote Originally Posted by pBS View Post
    hmmm,seems i have to do dpkg line, then apt-get -f install, then dpkg line again for it to not have problems with dependancies...?
    still just black screen after hitting my server ip.
    formatted another card and tried twice, same exact results..[on an RPI2]
    Listing missing dependencies is correct behavior but a single sudo apt-get -f install AFTER should do the trick.
    -Never mind you got it installed eventually.


    Quote Originally Posted by pBS View Post
    hmm,maybe a newa problem? it wasn't working for browser.
    i re-setup newa from scratch, now working in browser... still same black screen and forbidden in log..

    web.log from server:
    Code:
    [...startup]
    2017-04-18 21:13:53.854	[DEBUG][19]	Starting webserver for IPv6/IPv4
    2017-04-18 21:13:54.505	[INFO][16]	About to connect to remote recording service
    2017-04-18 21:13:54.533	[DEBUG][16]	RecordingServiceProxy@exit
    2017-04-18 21:13:54.534	[DEBUG][16]	Got Web Request (::ffff:192.123.1.129): /control    key=-1&size=960x540&client=sdl.RPI3.940b8:27:eb:4c:95:74&quality=high&sid=792cef595d1b4a6aa58dc3ec9a9eb278
    2017-04-18 21:13:54.545	[DEBUG][16]	403 Forbidden
    2017-04-18 21:13:54.572	[DEBUG][19]	Got Web Request (::ffff:192.123.1.129): /activity    format=json&client=sdl.RPI3.940b8:27:eb:4c:95:74&time=1453566159131&sid=792cef595d1b4a6aa58dc3ec9a9eb278
    2017-04-18 21:13:54.575	[DEBUG][19]	403 Forbidden
    2017-04-18 21:14:01.485	[DEBUG][17]	Got Web Request (::ffff:192.123.1.129): /control    key=-1&size=960x540&client=sdl.RPI3.940b8:27:eb:4c:95:74&quality=high&sid=792cef595d1b4a6aa58dc3ec9a9eb278
    2017-04-18 21:14:01.485	[DEBUG][17]	403 Forbidden
    2017-04-18 21:14:01.510	[DEBUG][19]	Got Web Request (::ffff:192.123.1.129): /activity    format=json&client=sdl.RPI3.940b8:27:eb:4c:95:74&time=1453566159131&sid=792cef595d1b4a6aa58dc3ec9a9eb278
    2017-04-18 21:14:01.511	[DEBUG][19]	403 Forbidden
    Client is probably correct installed and working in a sense.
    But, I have no idea why the requests are forbidden. The urls got a sid which suggests the client has connected with NPVR server and got a session.
    If you have set a custom pin code in NPVR that may be the cause, but I canít see how you would get a sid in that case.

    Maybe sub or mvallevand can help us with this one from dealing with similar clients.

    /Fred

  5. #25
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    89,169
    Isn't 192.123.1.129 a public Internet address range, rather than a LAN NAT address range (ie, normally it'd be 192.168.x.x)? If so, it's probably a case of needing to tick the 'allow remote access' tickbox.

  6. #26
    Join Date
    Aug 2005
    Location
    Houston
    Posts
    4,796
    i do have that box checked.. and as far as i know 192.123.x.x is local only,[unroutable] but i might be wrong on that..
    hmm,i swear i remember reading that they were also reserved for private networking, has worked here for 10 years w no problems..on several routers.

    seems it's owned by Kraft foods..
    didnt really wanna change that cuz it's all throughout the network here..and this is the first thing that's complained so far..
    is there anything hardcoded for 192.168.x.x?

    interestingly, newa works fine from lan machine using name 'pvr2:8866' but guide and livetv screens don't work when using ip address [192.123.1.8:8866]...?
    Last edited by pBS; 2017-04-19 at 06:20 PM.
    Hardware: HDHR Prime, HDPVR 1212, Raspberry pi2, VFD display w/LCDSmartie

  7. #27
    Join Date
    May 2006
    Location
    Canada
    Posts
    27,732
    That is definitely not a private IP. You probably need to change the PIN from 0000 on public IP's too.

    Martin

  8. #28
    Join Date
    Aug 2005
    Location
    Houston
    Posts
    4,796
    that may be it...probably why my newa on other machines has been so finicky..
    i'll try a quick test to see, but i bet there's something in newa that is hardcoded to only allow 192.168.x.x for certain things..
    and since it's not really an external public ip, the checkbox may not work right in this case.
    Hardware: HDHR Prime, HDPVR 1212, Raspberry pi2, VFD display w/LCDSmartie

  9. #29
    Join Date
    Nov 2003
    Location
    NextPVR HQ, Wellington, New Zealand
    Posts
    89,169
    Quote Originally Posted by pBS View Post
    i do have that box checked.. and as far as i know 192.123.x.x is local only,[unroutable] but i might be wrong on that..
    hmm,i swear i remember reading that they were also reserved for private networking, has worked here for 10 years w no problems..on several routers.

    seems it's owned by Kraft foods..
    didnt really wanna change that cuz it's all throughout the network here..and this is the first thing that's complained so far..
    Honestly, I think you're very lucky if this hasn't caused issues. You should think about changing it to one of the private IP address ranges.

    is there anything hardcoded for 192.168.x.x?
    No, but you will fail the checks that determine if you're on a private local network vs the public internet.

    ...and, when it's receiving requests from the public internet it expects the client to login, supplying pin number, and non-default 0000 etc. I'm not sure if Fred's new client does this login. If he'd only been expecting it to be used on the local network, it may not have code for doing this. That snippet of log shown above shows it attempting to use the API without logging in, so this may be your problem....

  10. #30
    Join Date
    Aug 2005
    Location
    Houston
    Posts
    4,796
    yep...i edited <autologinNetworks> in config-web.xml and now it lets lan machines access newa using ip address, but still no go on pi...
    [edit] my mistake, browser cached it so no it didn't help editing config-web.xml [edit]
    i do suspect that is the case..checks for public ip ranges stuffing it up..

    i'll reset my ip range and test to see...have a feeling it'll solve things with this and the nlite program too..thanks
    Last edited by pBS; 2017-04-19 at 07:32 PM.
    Hardware: HDHR Prime, HDPVR 1212, Raspberry pi2, VFD display w/LCDSmartie

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •