AllowRemoteStreaming necessary for connecting remotely with the Android Client?

[mmortal03]

What does having the setting AllowRemoteStreaming set to true actually do, and does it need to be set to true to connect remotely with the NextPVR Android Client from the Play Store?

[sub]

Pretty sure it does need to be set true for remote access. You also need to have pin changed from the default 0000

[mmortal03]

Pretty sure it does need to be set true for remote access. You also need to have pin changed from the default 0000

Weird, but after further testing, it may not need to be set to true. I've got it set to false, and NextPVR Android Client still works (made sure to reboot the server with the updated config file, and configured the Android Client from scratch to make sure).

The problem was that I was using a 12-character alphanumeric PIN (not the password, to be sure, that's separate), and, while this worked fine with Kodi, it did not work with the Android Client. Not sure if it's the number of characters or the upper/lowercase letters or what.

Maybe you have an idea what the PIN character limitations are? Once I know, I can go in to all my Kodi instances and change it to something else that's still secure, but also works with the Android Client.

[mvallevand]

Weird, but after further testing, it may not need to be set to true. I've got it set to false, and NextPVR Android Client still works (made sure to reboot the server with the updated config file, and configured the Android Client from scratch to make sure).

Maybe you are running a reverse proxy.   I tried to remote today with Kodi and when it is false, I couldn't connect. The logs had

2025-03-11 14:17:25.203 [DEBUG][17] Remote connection not allowed. Pin login failed.

A reverse proxy to NextPVR can make it like you are running on localhost.

Martin

[mmortal03]

Maybe you are running a reverse proxy.   I tried to remote today with Kodi and when it is false, I couldn't connect. The logs had

2025-03-11 14:17:25.203 [DEBUG][17] Remote connection not allowed. Pin login failed.

A reverse proxy to NextPVR can make it like you are running on localhost.

Martin

That isn't something I'm doing intentionally, if it's acting that way. My NextPVR server is simply running on a Windows computer that is connected by Ethernet to my router, and my router is port forwarding port 8866. The NextPVR Android Client was connected over LTE data (WiFi was turned off).

Not sure if any of the other settings would change your test results (maybe some of these overlap)?:

    <AllowRemoteAPI>true</AllowRemoteAPI>
    <AllowRemoteStreaming>false</AllowRemoteStreaming>
    <AllowRemoteTranscode>true</AllowRemoteTranscode>
    <AllowUnauthenticatedStreaming>false</AllowUnauthenticatedStreaming>


I'm willing to help get to the bottom of it, but I do believe my main issue still comes down to some sort of PIN character limitation of the NextPVR Android Client, because changing it to a short, all numeric PIN got it working for me (but I'd obviously not like to have my PIN that is exposed to the Internet be a short, all numeric PIN, so I'm hoping to find out what the PIN limitations are).

[mvallevand]

Sorry I was thinking Allow Remote Access in the web settings. AllowRemoteStreaming seems to be a remnant from v4 as I noted here https://forums.nextpvr.com/showthread.ph...#pid596913 when I tested it I don't think it did anything. Since I had a remote server set up I tested again today and it still doesn't do anything.

AllowUnauthenticatedStreaming = true with AllowRemoteAPI = true does much the same thing for the /live and /stream interfaces for streaming without a SID from the API.

Martin