No guide images using reverse https proxy

[QDivision]

Hi @mvallevand

I am running Kodi 20.2 and have NextPVR running behind an nginx proxy (https).

I have set the plugin to use HTTPS protocol using the XML settings file (it would be great if this setting was user facing) everything seems to run smoothly however the guide images are not fetched (and recordings) strangly if I set the 'remote access' feature the recording images do get fetched but still not the guide. I am unsure what the remote access feature actually does since the reverse proxy would handle all connection forwarding?

Is there a reason why guide images do not work remotely?

Thanks

[mvallevand]

Given it is not a simple matter to configure NextPVR as https server and to configure Kodi to use self signed certificates I have no plans to expose the https configuration since it would likely cause more support.

Remote access is required if NextPVR code determines the client is not on the local LAN. The NextPVR logs should help to identify that.

For the guide problem I would need to see the NextPVR logs and Kodi debug log. The code should be sending the sid as it does for recordings. I already discourage using guide based art but that is especially true with remote connections because each episode image is cached, but the session sid will mean there are multiple images for each sid.

Martin

[QDivision]

I'm using proper signed certs rather than self signed but understand why you don't want to expose the setting.

The client will look like a local client due to the reverse proxy even though it's running remote which is probably why the setting has little effect, although is odd why enabling it causes the recording images to work.

I will look to get some logs to post

[mvallevand]

Agreed reverse proxy can be make it appear as local LAN, which is a potential issue when users aren't aware of this. What if you change the PIN to 0000 and disable remote?

Martin

[QDivision]

Attached is the Kodi, relevant lines seem to be:

2023-08-05 16:11:32.288 T:12283  debug <general>: CCurlFile::GetMimeType - <https://pvr.redacted.uk:443/service?method=channel.show.artwork&name=Live%3A%20UCI%20Cycling%20World%20Championships&prefer=landscape> ->
2023-08-05 16:11:32.291 T:12283  debug <general>: CurlFile::Open - <https://pvr.redacted.uk:443/service?method=channel.show.artwork&name=Live%3A%20UCI%20Cycling%20World%20Championships&prefer=landscape>
2023-08-05 16:11:32.340 T:12284  error <general>: Could not find suitable input format: application/octet-stream
2023-08-05 16:11:32.478 T:12283  debug <general>: LoadFromFileInternal - Load of https://pvr.redacted.uk:443/service?meth...=landscape failed.

the URL works in my browser (once logged in to NPVR session)

[QDivision]

Setting the PIN to 0000 stops the plugin working (says pin incorrect) however I believe this is due to either the plugin or NPVR not allowing 0000 over a remote connection (even though the reverse proxy should be masking this?).

[mvallevand]

After the session is opened the browser would use a stored session sid. Test with curl.

NextPVR seems to be blocking it without the sid that is why I asked to test with PIN 0000 on server and client of course.

Martin

[QDivision]

I changed to 0000 on server and client but the plugin fails to login.

It looks like the sid is not included in the URL request, which would return an invalid session XML response. Is it possible to add the sid to the requests?

[mvallevand]

Ok clearly NextPVR is not seeing your connection as local.

I found the issue in the pvr.nextpvr code. Guide art was forced off when remote and PIN was not 0000.

Martin

[QDivision]

Ok, will this be fixed in the next release or will you have a version I can test to confirm the fix?