DVB-S2 scan succeeds, channels save to DB correctly, but playback fails — adapter0-DVB-S-channels.conf is never created.
NextPVR 7.1.1.260616, Ubuntu 25 (native install via nextpvr-helper.deb), tuner is a Hauppauge WinTV-Starburst2 (Montage M88RS6000 demod, cx23885 driver) — confirmed working via
Code:
dvbv5-zap
outside NextPVR (locks cleanly, correct signal/CN).
Channel scan (Single Satellite, custom Optus-D1-160.0E scan file) completes successfully — 21 channels appear correctly in the UI and in
Code:
npvr.db3
(
Code:
CHANNEL_MAPPING.tuning
is populated with correct DVB-S2 tuning XML for each channel).
Playback always fails with "No tuner was available for the requested channel."
Code:
device-adapter0.log
shows the actual cause:
Code:
[ERROR] Failed to get tuning params for (ChannelName) from /var/opt/nextpvr/adapter0-DVB-S-channels.conf
That file is never present on disk — confirmed via
Code:
find / -iname "*channels.conf"
after multiple fresh scans. The scan log shows a temporary
Code:
adapter0-DVB-S-channels-scan.conf
is used during scanning:
Code:
GOT: Channel config will be saved to /var/opt/nextpvr/adapter0-DVB-S-channels-scan.conf
but the final non-
Code:
-scan
file that
Code:
DeviceHostLinux
reads at stream-start time is never written by the save step.
Logs attached (Settings → About → Log Files).
Hi, I'm new to IPTV and I've just setup nextpvr on a Synology DS218+.
All is working well except for channel 9 and 9GEM. They give me "Streaming Failed (transcoder exited)" when viewed on a Windows 11 PC and similar on an Apple TV 4k.
I tried nextpvr on the Windows pc, the streams load but then hang. I have a good internet connection (500\50).
I have had this issue since I started using NextPVR
My donation status disappears, and thus the channels available to watch (and more importantly record) go away. This disrupts the recording schedule, even after restoration of the donation status.
Recently, it has become problematic to register that I have donated, as seen in the attached screenshot.
I am struggling with using the NextPVR app and Wireguard VPN enabled on the router. When I switch on Wireguard then I can access the NextPVR server (with the Android phone) on the home network using the browser (i.e. 192.168.1.5:8866) meaning access is working with Wireguard.
But when I try the app with the local server installed (IP: 192.168.1.5 and Pincode) then I get an error Failed to connect to NextPVR server. Why is that?
I have a problem, it's not the fault of NextPVR, but it's stopping me using NextPVR and folk here might be able to help.
When upgrading my Windows 11 23h2 installation to 24h2 or 25h2, waketimers cease to function. In other words NextPVR cannot wake the machine to start recording. But it's not just NextPVR, a simple batch file to echo to a log, run as a scheduled task with "wake to run" enabled... also will not wake the PC. Mouse & keyboard still wake from sleep, no problem there.
I've done all the usual: disabled hibernation, allowed waketimers, checked (and experimented) with BIOS settings, blah blah blah. Seriously, I've spent many hours on this. I've even gone so far as to wipe my machine (after taking a full backup) to install 25h2 brand new, fresh, out of the box. Still doesn't work. Oh, and of course for the upgraded and the new install I've tried using the manufacturer recommended chipset drivers and I've tried the latest Intel drivers. No joy.
The motherboard is a Gigabyte Aorus Elite AX 1.0 Z790, (I've tried with previous and latest BIOS versions).
My question is then, is there anyone out there successfully running waketimers on Windows 11 24h2 or 25h2 *and* on a Z790 motherboard? Anyone at all? And, bonus question, is it a Gigabyte 'Aorus' motherboard of some flavour? Because I've spent so many hours on this and I'm wondering if I should just bin the motherboard and swap it out for some other make (problem being that I don't want to have to buy new RAM/CPU as well).
Thanks! Right, now to pen a second question...
I'm having an IPTV problem which I think I have narrowed down to how NextPVR handles the User-Agent header for XC/M3U requests and live M3U8 streams.
This IPTV account still works correctly in TiviMate using Xtream Codes, but recently stopped working properly in NextPVR.
The original symptom in the NextPVR web player was:
Streaming Failed (transcoder exited)
After troubleshooting it, I think I have found a reproducible User-Agent issue.
SETUP
- NextPVR on Windows 10
- IPTV provider configured in NextPVR
- Same account/server works in TiviMate using "Xtream Codes parameters"
- Provider credentials are active and valid
- Account allows 2 connections
- Server/username/password omitted from this post
1. EXISTING NEXTPVR CHANNELS STOPPED WORKING
When trying to play a channel in the web player, NextPVR could not start the IPTV stream.
The eventual FFmpeg 404 was from NextPVR's own local /live URL, for example:
The important part of nrecord.log was earlier in the chain:
IPTV StartStream
Checking m3u8 stream (...)
Unable to StartStream(): One or more errors occurred. (A task was canceled.)
StartStream(...) allocated handle: 0
Handle: 0
Failed to start stream. Handle 0.
So the FFmpeg/transcoder error appears to be a consequence of the IPTV source failing to start, rather than an encoding problem.
2. "UPDATE CHANNELS" ALSO FAILED
Trying to update the existing IPTV source gave an empty "0 of 0 selected" channel list.
nrecord.log showed NextPVR attempting the provider M3U URL and receiving:
Downloading m3u https://<server>/get.php?....
Failed to download channel list:
System.Net.Http.HttpRequestException:
Response status code does not indicate success: 404 (Not Found).
at NShared.Recorders.IPTVScanner.WorkerThread()
However, the service is still active and working in TiviMate.
3. XC IMPORT ALSO RETURNS ZERO CHANNELS
I then tried adding a new IPTV device using "Import Using XC", entering the same server, username and password used by TiviMate.
NextPVR briefly showed "Logging in", then returned 0 channels.
The log showed the XC login failing with HTTP 404 in WebClient.DownloadString(), inside IPTVScanner.XCWorkerThread().
The same Xtream API endpoints work successfully in Chrome:
The file is valid, starts with #EXTM3U, and contains the current channel URLs.
I imported this local M3U into a new NextPVR IPTV device successfully.
So the playlist itself is fine once it has been downloaded with a User-Agent.
6. THE ACTUAL LIVE STREAM ALSO REQUIRES A USER-AGENT
I then extracted one current M3U8 stream URL from the new playlist and tested that independently with System.Net.WebClient.
Without a User-Agent:
NO USER-AGENT: FAILED
The remote server returned an error: (404) Not Found.
With:
$wc.Headers["User-Agent"] = "Mozilla/5.0"
the exact same stream URL succeeds.
So the User-Agent requirement is not limited to the XC API or get.php download. It also applies to the actual live M3U8 stream.
7. LOCAL M3U WITH #EXTVLCOPT USER-AGENT
I created a one-channel M3U to test this in isolation:
#EXTM3U
#EXTINF:-1 tvg-name="LBW: HBO UA TEST",LBW: HBO UA TEST
#EXTVLCOPT:http-user-agent=Mozilla/5.0
http://<stream-server>/live/USERNAME/PASSWORD/STREAMID.m3u8
NextPVR imported this successfully.
When I tried to play it, NextPVR got as far as attempting the IPTV stream:
It remained at "Starting Device. Please Wait..." for several seconds and then:
Unable to StartStream(): One or more errors occurred. (A task was canceled.)
StartStream(...:LBW: HBO UA TEST, ...) allocated handle: 0
Handle: 0
Failed to start stream. Handle 0.
The web player then showed "Streaming Failed (transcoder exited)".
8. TEST WITH |user-agent=Mozilla/5.0
I then created another one-channel test using the pipe/header syntax:
System.NullReferenceException: Object reference not set to an instance of an object.
at NShared.Extend.RequestHandlers.TranscoderHLS.InitiateTranscode(String& reason)
at NShared.Extend.ChannelRequestHandler.InitiateTranscode(Dictionary`2 parameters)
at NShared.Extend.ChannelRequestHandler.HandleRequest(String method, Dictionary`2 parameters)
at NShared.Extend.PluginFactory.HandleRequest(ServiceResponseStream serviceResponseStream, Dictionary`2 parameters)
at NPVR.Controllers.ServicesController.HandleServiceRequest(String body, String contentType)
So the |user-agent syntax appears to trigger a NullReferenceException inside TranscoderHLS.InitiateTranscode() in my setup.
SUMMARY
As far as I can tell:
1. The IPTV provider now requires an acceptable User-Agent.
2. Requests without one appear to deliberately receive HTTP 404.
3. I can reproduce this independently using System.Net.WebClient:
- no User-Agent = 404
- Mozilla/5.0 = success
4. This applies to:
- player_api.php / XC login
- get.php / M3U download
- the actual live M3U8 stream
5. This explains why TiviMate and Chrome work while NextPVR's XC/M3U requests fail.
6. Downloading the M3U manually with a User-Agent allows NextPVR to import the current channel list.
7. Adding #EXTVLCOPT:http-user-agent=Mozilla/5.0 does not allow the live stream to start.
8. Using:
|user-agent=Mozilla/5.0
causes a NullReferenceException inside:
NShared.Extend.RequestHandlers.TranscoderHLS.InitiateTranscode()
Would it be possible for NextPVR to send a normal User-Agent for:
Hello,
I've been configuring NextPVR Server to use https instead of simply http with a certificate I created for it (I manage my DNS server and my certificates' infrastructure for many services), and everything seems to be working fine except with the Kodi add-on.
Scenario:
Windows 11 with both NextPVR and Kodi.
NextPVR launched not as a service but as a scheduled task, with the PFX and the pvt.key's password passed as parameters.
NextPVR is fully functional via browser (FireFox) using https; channels can be watched without problems (after granting audio+video permission)
After enabling the corresponding setting, NextPVR works as a M3U provider via https to clients such as VLC. NOTE: VLC for Android was not capable of verifying the certificate's chain because Android installs users' CA certificates (like mine) apart from the system ones, and not all apps are configured to check at both sites (this has happened to me already in the past with other apps; fortunately VLC pops up a warning giving the option of trusting the certificate anyway, but this is 100% a VLC thing)
But when it came to Kodi with the NextPVR add-on (after tuning the settings.xml file - in fact I also tuned the "instance-settings-1.xml" file), Kodi shows the following message on the top-right corner: "PVR Manager is starting up 0%" and stays there forever. NOTE: Despite being both Kodi and NextPVR running on the same PC, the add-on is not configured with "localhost" or 127.0.0.1 but with the URI associated with the certificate. This should not be the problem as my switch is capable of managing loopbacks in the domain (in fact, it is also how I checked via browser, also on the same Windows PC, which worked perfectly).
These are the versions I'm running:
NextPVR: 7.1.1.260616
Kodi: 21.3.0
add-on: 21.3.2
PS: I've noticed that it is encouraged to use a reversed proxy instead of using SSL directly on NextPVR; however, any help would be highly appreciated.
I have NextPVR server and Kodi add-on working pretty well, but noticed I lost the ability to mute or change volume from the web interface -or- audio icon at the top of the screen when watching Live TV (IP channels are not affected). Did I miss a setting to enable this or is the feature not available?