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.
Thank you very much in advance
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.
Thank you very much in advance
