Can't connect to http://127.0.0.1:8866/ on Xubuntu 22.04

[rakircher]

I changed it to /tmp/ in web Settings and it makes "Available Storage " work right. It sort of makes sense because that is the directory that the old legacy Windows NPVR used.

This is scary! Am I the first person to use this Linux NextPVR v5 version or what?

[mvallevand]

Yes and no, but several issues are in play.

You had a unique issue with very poor network access that cannot be addressed by any installer.

You are the first "user" that I know of that used a hack to install libssl 1.12 to get this working on 22.04 I suspect many are waiting for a supported version.

You are certainly not the first user to not read the information about setting file permission properly. That is configuration not the installer

Also there was a controversial change in Ubuntu 21.04 https://discourse.ubuntu.com/t/private-h...ards/19533 shifting from a desktop to server model that also breaks the mechanism the installer uses for creating the default recording and live tv sub-directoris. This was something I was going to address for the NextPVR v6 installer, but I didn't see it needed for v5 because of the dotnet ssl issue.

Of course your solution of using /tmp for recordings is quite serious since that folder is removed after every reboot, so you have more reading to do.

Martin

[sub]

2022-06-27 18:20:16.715 [DEBUG][5] Checking disk space for: /home/dick/NextPVR/Recordings/
2022-06-27 18:20:16.729 [ERROR][5] Unexpected error querying available disk space (/home/dick/NextPVR/Recordings/): System.UnauthorizedAccessException: Access to the path is denied.

As Martin said, don't use /tmp/, but you will need to set it to somewhere NextPVR has permission to see. In your case it doesn't have permission to see in your /home/dick directory.

[rakircher]

I used /tmp/ just to see if the "Available Storage" problem was "permissions" because I knew NextPVR had permissions to that directory. Thanks for telling me that /tmp/ was a bad choice. I have changed it to /Storage/Recordings/ and /Storage/Live_TV_Buffer. Not my favorite place because I don't like to change the "standard" Linux directory tree, and putting it in /home/dick/NextPVR/Recordings does not work.

I tested /Storage/Recordings.... by putting large junk files into those directories with external Thunar file manager and it works, but only when I restart the NextPVR web using my browser. If I make storage changes (more or less), I can't make it show up on the "Available Storage display (by using the browser's back arrow key, for example). I think that is a shortcoming of NextPVR because I would normally leave the computer on all the time and not restart it very often in normal operation.

I don't have the Recordings working yet, so maybe it works differently when Storage changes caused by new recordings saved internally by NextPVR occur. Time will tell.

[sub]

Not all Linux distros are created equal. Previous versions of Ubuntu have no problem with you having the recording directory there. Unfortunately they changed some significant stuff in the recently release ubuntu 22.04 and broke it. We've got a workaround coming in the next release.

[mvallevand]

Not my favorite place because I don't like to change the "standard" Linux directory tree, and putting it in /home/dick/NextPVR/Recordings does not work.

It does work though if you change the "standard" security permissions.    There is a script included with the deb file to set the permissions for the base folders

sudo /opt/nextpvr/shell/nextpvr-recording.sh /home/dick/NextPVR
sudo /opt/nextpvr/shell/nextpvr-recording.sh /home/dick/Recordings
sudo /opt/nextpvr/shell/nextpvr-recording.sh /home/dick/Live_TV_Buffers

These 3 folder names aren't the names created by NextPVR so this could never be automated.

The Canonical change I noted is only user dick has access to /home/dick now so you need to allow other users to have access to files in it.  (Changing from the default 750)

sudo chmod 755 /home/dick

It is this last line that will be added to the futureinstall script.  If you had done this before running the deb installer the first time, you would have not the default nextpvr folders created.  You can make this more secure if you to lock this down harder, the nextpvr user only needs execute access to for directory searches.

Martin

[rakircher]

I can't do a NTSC OTA Channel Scan.  NextPVR seems to be scanning QAM channels instead, and  is NOT working properly as should be seen in the attached log files.

While my WinTV-DualHD tuner was on order and being shipped, I installed the Hauppauge PPA (software and firmware) to assure compatibility with the tuner.  I installed the PPA while running with the 5.17 kernel because the Ubuntu 22.04 original 5.15 kernel has a Network bug that causes my Internet connection to drop as often as every 1.5-minutes. 

I expected the PPA to be installed into the running 5.17 kernel since I had no choice, but instead it was installed into a modified 2nd version a 5.15 version kernel leaving the original 5.15 as a GRUB boot choice.  I reported the problem to Hauppauge.com and they responded in less than a day saying they would send me a PPA for the 5.17 kernel next week (which is now this week).  Incidentally, Hauppauge also said that Ubuntu  22.04 should be ready to use with the WinTV-DualHD tuner without need for the PPA, but they still recommend installing the PPA as I did.

I plugged the new WinTV-DualHD tuner into a USB port with OTA TV antenna attached.  It should be auto-detected and install itself according to documentation.  Attached are Terminal logs that show Ubuntu, using the "lshw" command detects both my old WinTV 3600 tuner and the new tuner.

Using the NextPVR web program, I tried "ReScan For Devices", but it adds nothing (see Terminal Logs) except duplicate lines which are for "QAM" (I don't have Cable TV).  There is a "Keep digital tuners primed" check box ---  not sure what it does, but I tried it both ways.  The "Scan Channels" button seems to make it scan something, but it is not the NTSC OTA channels.  Also I tried booting the computer for each of the 3-kernels, and none work to Scan NTSCScan Channels.

My guess is that NextPVR is not detecting my WinTV-DualHD tuner.  Is there a special way that I can view the NPVR Logs (.zip file).  The individual files in the zip file have 000 permission which is no privileges for read, write, or execute.  I tried searching "how to read npvr log files" and found nothing relevant.  Any help would be greatly appreciated.

[rakircher]

My previous message said "NTSC" in ERROR. I meant to say "ATSC".

[sub]

I'm fairly sure with the Ubuntu 18.04 / 20.04 / 22.04 I plugged it in, ran dmesg and saw a missing firmware file listed, then downloaded that file and copied it to /lib/firmware, then removed and plugged the device back in and it was fully functioning. I didn't install PPA.

[sub]

Local Devices: <devices>
<device>
<name>adapter2/frontend0 (LG Electronics LGDT3306A VSB/QAM Frontend)</name>
<type>ATSC</type>
<filter>adapter2/frontend0</filter>
<instance>1</instance>
<resource>adapter2</resource>
</device>
<device>
<name>adapter2/frontend0 (LG Electronics LGDT3306A VSB/QAM Frontend)</name>
<type>QAM</type>
<filter>adapter2/frontend0</filter>
<instance>1</instance>
<resource>adapter2</resource>
</device>
<device>
<name>adapter1/frontend0 (LG Electronics LGDT3306A VSB/QAM Frontend)</name>
<type>ATSC</type>
<filter>adapter1/frontend0</filter>
<instance>1</instance>
<resource>adapter1</resource>
</device>
<device>
<name>adapter1/frontend0 (LG Electronics LGDT3306A VSB/QAM Frontend)</name>
<type>QAM</type>
<filter>adapter1/frontend0</filter>
<instance>1</instance>
<resource>adapter1</resource>
</device>
<device>
<name>adapter0/frontend0 (Samsung S5H1409 QAM/8VSB Frontend)</name>
<type>ATSC</type>
<filter>adapter0/frontend0</filter>
<instance>1</instance>
<resource>adapter0</resource>
</device>
<device>
<name>adapter0/frontend0 (Samsung S5H1409 QAM/8VSB Frontend)</name>
<type>QAM</type>
<filter>adapter0/frontend0</filter>
<instance>1</instance>
<resource>adapter0</resource>
</device>
</devices>

It looks like it's detecting both ATSC and QAM tuners.