I have recently installed a August DVB-T210 usb stick and the recommended software NextPVR. Its a new HP Z2 G9 workstaion running windows 11.
Had a few installation issues getting webapp and NextPVR working. However I have a problem when the PC is first powered on. I get the error "Starting device: please wait" and later "streaming failed (transcode exited).
Seems the software cant start the device. I have tried turning off the security software HP Wolf Security then exited Edge browser and tried again; This sometimes solves the problem but means 20mins getting NextPVR working each time pc is turned on.
There is also a close down issue that shows as NextTV Backend says its recording and this stops shutdown. There are no scheduled recordings.
Seems like the USB stick is reluctant to start.
Have check firewall and NextPVR features and USB stick is in a USB 2 port 480Mbps.
The version of NextPVR is ver 7.0.1.241229
Hi. I noticed the release under the latest tag hasn't been updated in docker hub in two months, but stable has with the newest release.
Is the latest tag no longer maintained for the latest release?
Apparently Schedules direct is getting hammered with requests as they put a 24 hr hold on my account. I do not use jellyfin. the only thing connecting to sd should be 2 instances of npvr on separate machines, on the same lan. I just updated from the November build to the current one so I am not sure in which the problem lies. Any help would be apprecieated. I just filed a ticket with sd. logs attached.
I've got NextPVR set up and running on my Ubuntu 24.04/Firefox system but I'm having an issue with the duration displayed on the timeline during playback (see attached image).
The left edge starts our showing 00:00:00 as it should and if you hit play it starts counting up the seconds as it should.
The problem occurs if you hit the skip forward button. It seems to skip forward 30 seconds but the timeline shows it skipping forward 2 minutes. If I click the timeline to move forward to near the end of the recording it shows approximately twice as many minutes as it should.
For example the image below shows a recording of 03:33:00 on the right side of the timeline, which is correct, but an elapsed time on the left side as 06:55:01 wich is basically double what it should be.
Any clues! Is there a setting somewhere I need to change?
I've been testing for the past few days trying to setup extras.xml
i've been sucessful in setting it up but theres a few more pains to figure out.
Namely channel management.
My provider stores a database of channels in a authenticated json request, i've managed to scrape it fully.
Since they provide both channels for UK and Poland, i wanted to keep it split up to make assigning channel groups easier.
Is there anyway to seperate out extras channel based on what file they're from?
A related question would be if theres a way to update channels without nuking all the groups, as it's a pain to sort through so many channels.
I’m running NextPVR (version 7.0.0.241105) in a Docker container behind a Caddy (version v2.9.1) reverse proxy for SSL termination. Everything works fine initially, but I’m encountering a persistent issue related to session handling. Specifically, I’m seeing the following errors in the NextPVR logs:
2025-01-10 17:00:32.152 [DEBUG][67] host_callback: ...
2025-01-10 17:00:32.152 [ERROR][67] Rejecting sid. Different IP address. (100.64.0.5:61473 vs 100.64.0.5:61411)
2025-01-10 17:00:32.152 [DEBUG][63] parameters:
2025-01-10 17:00:32.152 [DEBUG][67] {"stat":"Failed","code":8,"msg":"Invalid Session."}
The problem occurs when using the Web Player in Chrome.
The Problem
It appears that Caddy is changing the source port for requests during a session, which causes NextPVR to treat them as different sessions and reject them.
Question
I’m looking for advice on the following: • Has anyone encountered similar issues when running NextPVR behind a reverse proxy like Caddy? • Is there a way to configure NextPVR to ignore the source port when validating sessions? • What’s the recommended way to configure Caddy to prevent this issue with session handling? • Are there any tips or workarounds to ensure stable session management in this setup?
services:
nextpvr:
image: nextpvr/nextpvr_amd64:latest
container_name: mtv
volumes:
- /home/user/container/data/nextpvr/config:/config
- /home/user/container/data/nextpvr/videos:/recordings
- /home/user/container/data/nextpvr/videos:/buffer
expose:
- "8866" # Exposes port 8866 for access within the Docker network
restart: unless-stopped
group_add:
- "993" # Change this to match your "render" host group id and remove this comment
devices:
- /dev/dri/renderD128:/dev/dri/renderD128
I'm trying to setup NextPVR and have a strange issue - If i can solve this i will have my perfect setup.
Im using Streammaster as a backend
If I try to channel up or down while watching something, if the new channel is part of the same IPTV subscription (1 connection) then it fails to turn over and goes back to the guide. If i come out of the channel and switch via the guide it works fine.
If i have channels on different IPTV providers it switches fine.
I can see from StreamMaster that the stream does stop before the next one trys to start
I see this issue in the native Next PVR client and Kodi
I tried pointing Kodi directly to StreamMaster via a IPTV plus in to see if the issue was with NextPVR or StreamMaster - When i do this the channel tuner over fine to the same IPTV provider so i think this is an issue with NextPVR rather than my backend
I have attached my NextPVR logs
I have checked that the timeshift was not enabled in Kodi but couldn't find a similar setting directly in NextPVR
I have tried an install of NextPVR on 2 windows machines and in Docker, I get the same result in them all.
Unable to test with none IPTV yet as I'm waiting for my tuners to arrive.
to try out with my Chromecast With Google TV uidroid setup & as they said they had RF connect ability I expected they would come with a USB RF receiver but they didn't.
I have had a play trying to pair them with the CCWGTV but no luck so far, I expect because I have no idea what buttons need to be pressed on the remotes to go into pairing mode. I also haven't been able to find anything helpful with a web search. Anyone got any idea what I can try??
Hello, am experiencing a rather weird issue, in that when using Kodi with Nextpvr addon, I have noticed that one of my channels will not display any guide data.
In last couple of days, I now notice that 2 channels no longer display guide data, and just get completely blank fields in the guide inside Kodi.
The weird bit is that if I view the web based guide inside NextPVR web interface, and inside UIdroid, and even in an IPTV client like Tivimate, all the guide data is present.
It is only the Kodi client that the guide data does not display.
It is so bewilderingly strange, that I hesitate to even bring it up.
Both the affected channels are DVB-T, and I have Nextpvr set to grab DVB data for the guide sources.
The channels are Sky Open, and Trackside2. (both New Zealand DVB-T channels here)
I also can access the Trackside2 channel as a Colossus STB channel from a Sky Box, and obtain data by scraping to an XMLTV file for those STB derived channels, but just use NextPVR's own DVB guide gathering for the DVB-T side of things.
I tried nuking Kodi on a client, and reinstalling and configuring from scratch, and the same thing occurs and the guide for those channels is blank.
Yet, from the NextPVR web interface, the guide data for the affected channels is present, and likewise in the other clients I have tried. It is just Kodi NextPVR addon that is affected.
Any ideas as to what might cause this strange behavior?
but unfortunately the URI requires two cookies and some headers.
I haven't been able to make NextPVR accept passed cookies and I am not sure if NextPVR uses passed headers either when it fetches the key either, I couldn't see any logging on getting the key.
My first wishlist is that cookies could accepted from Extras (I and guess m3u8 files), perhaps using the Kodi method opf muitiple Set-Cookie= pipes on the url. These are huge though and in my use case only needed for the key.
My second wishlist which might be easier is providing an option allowing a override the URI. The extra could write the key to file and NextPVR could use that files instead of the URI to get the key.
