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

[mvallevand]

Sub he needs to do a fresh install so things get installed correctly if e wants to continue with the deb installer.

Martin

[sub]

Yep.

[rakircher]

The NPVR Help for Linux supported devices is:

Quote: "On Linux it supports IPTV, HDHomeRun, SAT>IP, digital tuners (DVB/ATSC/ISDBT/DMBT) that have kernel drivers available"

In your experience, would you think including Hauppauge's (ATSC) WinTV-DualHD device to NPVR's HELP be appropriate since Hauppauge's support includes PPA for Ubuntu?

Your answer to this question is critical to me because I am using Ubuntu for that reason, and I have found that OTA tuners from HDHomeRun have been discontinued and are now impossible to buy "new" from reputable Sellers. Also, I see a lot questions on the NextPVR Forums that include the WinTV-DualHB tuner, so I am hoping that with proper installation and debugging, it can me made to work with NPVR v5, and v6 in the future.

[sub]

In your experience, would you think including Hauppauge's (ATSC) WinTV-DualHD device to NPVR's HELP be appropriate since Hauppauge's support includes PPA for Ubuntu?

I regularly use the DVB-T version of WinTV-DualHD stick with Linux here. It's worked well for me.

Just now I briefly checked the ATSC version of the WinTV-DualHD on my Ubuntu (18.04) test machine, and it successfully found the device, was able to scan and find channels, and was able to watch the channel in the web app.

[rakircher]

The posts on my browser have gotten out of order.  I had a hanging post to edit that was already sent.  To get rid of it, I saved it as a draft and then could not delete it.  I refreshed browsers display and the posting numbers are correct again now.

This post of mine is intended to reply to Post #16 from Martin in which he suggested running the curl -s -v ...... command.  The attachment to this post is my Terminal Log  for running  this command.  It also includes rerunning curl -s only.  For it, I got the same result as before which is no response, no output, no errors.  The attached Terminal Log should explain everything.  The "verbose" run has a lot of information, and there are no errors.

There seems to be a misunderstanding about my attempted install using Debian months ago, and that I still having remnants in my current install that might be causing problems.  That Debian install was months before Post #1 in this thread.  I gave-up on my first attempt with Debian 11 because the NPVR install with it seemed hopeless and I could not make any progress.  There were absolutely no OS problems with Debian 11 itself, and I even had NPVR v5 running, no problem connecting to 8866, and no Login problems.  I gave up because I could not get anything working with NPVR.  Now I know it was because I could not scan with WinTV 1600 tuner, but back then I just gave-up contemplating going back to the legacy NPVR with Win 7 and a working WinTV 1600 tuner.  Finally, I decided not to back to Windows because it is too buggy.

Months later when I learned about Hauppauge PPA support for Ubuntu, I started over with a fresh new 1TB hard drive and installed Xubuntu 22.04 on it.  There was a post for not connecting to 8866 with Ubuntu 20.04.  My Post #1 started with the same subject title except I changed 22.04 to 22.04 and all else is in this current post.  Now I just have buggy Ubuntu 22.04 problems and the DotNet problem.  There are no remnants of a previous OS or a previous NPVR installation.

I can wipe everything clean again and go back to Debian 11, but with the bug fixes like the "apt command bug", that Martin fixed, I now only have one known bug with Ubuntu that is intermittently dropping my Internet connection.    The new 5.18 Linux kernel should fix it, so I would rather stick with Ubuntu because of the PPA support for Ubuntu that should make Hauppauge's WinTV-DualHD tuner work more easily with my limited skills.

[mvallevand]

I am not suggesting going back to Debian just run the clean up steps I gave you. I suspect at one time you ran as root not sudo which should always be avoided in Linux.

I do note in the curl -s verbose output 1.5 correctly. I can't explain why curl stopped displaying the version string (it did work in post#1) and it works on my 22.04 today Perhaps see if you have a .curlrc file somewhere. Also maybe the method you use to capture the terminal log is coming into play?

Martin

[rakircher]

There is no  .curlrc file (hidden or not) on my computer.  The missing "1.5" is somewhat explained at the end of Terminal Log.

I have gone thru all the postings to be sure I am up-to-date, and to answer any unanswered questions. You asked:
"How old is your motherboard? It must not be very recent if it still has ISA slots for the 1600."
For Linux, I don't think it is too old. The mobo is MSI N1996 with PCI bus expansion slots, video card plugged into PCI-e, and the WinTV-HVR-1600 ATSC/QAM/NTSC card plugged into the PCI slot.  It's home made and don't know the age.

You asked about how I capture the Terminal Log.  I make sure that the XFCE Terminal buffer is large enough, run the commands, and then copy results from the Terminal, and paste it into the Terminal Log file, and Zip it.

In your post #11, I do not understand: "That could be old cached data so try Ctrl F5 to clear it.".  I have not done this Ctrl F5 yet.  Do you mean F5 for the Firefox browser?

I was not sure if it was necessary to clear the contents of the "/tmp" directory before doing a fresh install. I saw nothing that might be a problem, so I left it as is and show the contents of /tmp in the Terminal Log.

This is the list of commands I ran to achieve a fresh install. (Log is attached)
ls -l /tmp/  # Get contents of "/tmp" for the log file
sudo apt remove nextpvr-helper  # clean out existing install
sudo apt purge nextpvr-helper
curl https://nextpvr.com/nextpvr-helper.deb -O  # Download the Installer file
sudo apt install ./nextpvr-helper.deb --install-recommends  # First time installation of the Installer
sudo dpkg -i nextpvr-helper.deb    # Upgrade to a newer version of the NextPVR application:

[mvallevand]

1. This time it failed before it completely installed the first time with that apt bug issue but that was also after a network error.

N: Download is performed unsandboxed as root as file '/home/dick/Downloads/nextpvr-v5/nextpvr-helper.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

It is quite possible that error is because of the network error but to be sure download the deb file to /tmp and install from there in the futre. There is no need to keep downloading the deb file.

2. Then it failed again on network curl error when you did the dpkg This command must only be run after a successful install

3. Then it failed again on on a second dpkg done in error it did return 1.5 but didn't download NPVR.zip

curl: (28) Failed to connect to nextpvr.com port 443 after 131141 ms: Connection timed out

4. Then you continued again with dpkg after those three failures with no network errors but because it was only partially set it up, it won't run correctly.

So you must do the clean up again and don't run dpkg unless the apt runs successfully.

You do need a more stable network to run this install. After the cleanup and before running apt I suggest running curl -s https://nextpvr.com/nextpvr-helper.txt to see the status. If it isn't 1.5 don't continue. As we saw in the logs that doesn't guarantee that the install will continue without other network errors.

Martin

[rakircher]

The original Ubuntu 22.04 LTS 5.15 Kernel is replaced with 5.17.5 to fix network problems.  Besides that, I used a wired Ethernet connection for this complete install from the beginning.  The word "error" did not appear during installation - please see the attached Terminal Log.

My browser connected to http://127.0.0.1:8866.  In "Settings", I setup storage locations: /home/dick/NextPVR/Live_TV_Buffer, and /home/dick/NextPVR/Recordings.  That's all I did.  The "Available Storage" is still showing: Default (0% free - 0.00GB), but it really does not matter to me if all else works after I purchase the WinTV-DualHD tuner and get it installed.

[mvallevand]

It still is failing.  The network error you get is not trapped because it would be very rare.  You did not try from /tmp as I suggested plus you continue to run dpkg when you should not.

Martin