IPTV Simple PVR reports 40x errors since upgrade to 2023.01-1

Help and Support
1

Hi,
I’m using IPTV Simple PVR client to stream from network.

Since OSMC upgrade to 2023.01-1 I get this error:
CCurlFile::Open failed with code 404 fetching a png, and
CCurlFile::Open failed with code 401 opening a stream

Here’s the full error message in kodi.log:

2023-03-12 14:09:10.442 T:3112    ERROR <general>: CCurlFile::Exists - Failed: Failure when receiving data from the peer(56) for http://<path_to_stream>/5412
2023-03-12 14:09:10.529 T:3112     INFO <general>: Skipped 1 duplicate messages..
2023-03-12 14:09:10.529 T:3112     INFO <general>: AddOnLog: pvr.iptvsimple: pvr.iptvsimple - GetChannelStreamProperties - Live Stream URL: http://<path_to_stream>/5412
2023-03-12 14:09:10.543 T:3112     INFO <general>: VideoPlayer::OpenFile: pvr://channels/tv/Alle%20Kan%c3%a4le/pvr.iptvsimple_1318614339.pvr
2023-03-12 14:09:10.546 T:3722     INFO <general>: Creating InputStream
2023-03-12 14:09:10.721 T:3722    ERROR <general>: CCurlFile::FillBuffer - Failed: HTTP returned error 401
2023-03-12 14:09:10.721 T:3722    ERROR <general>: CCurlFile::Open failed with code 401 for http://<path_to_stream>/5412:
2023-03-12 14:09:10.825 T:3722    ERROR <general>: CCurlFile::FillBuffer - Failed: HTTP returned error 401
2023-03-12 14:09:10.825 T:3722    ERROR <general>: CCurlFile::Open failed with code 401 for http://<path_to_stream>/5412:
2023-03-12 14:09:10.825 T:3722    ERROR <general>: CFileCache::Open - <http://<path_to_stream>/5412> failed to open
2023-03-12 14:09:10.825 T:3722    ERROR <general>: CVideoPlayer::OpenInputStream - error opening [pvr://channels/tv/Alle%20Kan%c3%a4le/pvr.iptvsimple_1318614339.pvr]
2023-03-12 14:09:10.825 T:3722     INFO <general>: CVideoPlayer::OnExit()
2023-03-12 14:09:10.840 T:3112     INFO <general>: Loading skin file: DialogConfirm.xml, load type: KEEP_IN_MEMORY
2023-03-12 14:09:10.850 T:3112     INFO <general>: CVideoPlayer::CloseFile()
2023-03-12 14:09:10.883 T:3112     INFO <general>: VideoPlayer: waiting for threads to exit
2023-03-12 14:09:10.883 T:3112     INFO <general>: VideoPlayer: finished waiting

I cannot reproduce this issue on PC using VLC, and this indicates a device specific error.

Please advise how to identify the root cause.

THX

2

Have you tested this on another Kodi installation, such as on PC?

Unfortunately without full logs it’s hard to see what’s going on.

Sam

3

No, I didn’t test on PC.

What other information is required from log?
I pasted all that is written to log in the relevant time window.

I have verified other streaming URL w/o authentication, and there’s no issue.
This confirms that addon IPTV Simple PVR client generally works, but it fails if URL includes authentication, means http://<path_to_provider>:8080/<user>/<password>/18392

Anyway, here’s complete kodi.log:
https://paste.kodi.tv/obasoteray.kodi

4

I have flashed OSMC version 20221001 on my Vero 4k and started setup from scratch.

I can report that IPTV Simple PVR works before running sudo apt dist-upgrade.

This means the root cause of this issue is not the *.m3u file and it’s content, because this file has not changed.
And there’s no restriction of streaming provider to block Kodi.

Instead the root cause must be related either to addon IPTV Simple Client and/or Kodi; I’m currently using IPTV Simple Client version 19.2.2 and Kodi version 19.4.

5

I have reproduced this issue on 2 other devices Vero 4K:
After installing latest upgrade IPTV Simple PVR reports 401 error opening a stream.

Is there anybody who’s accepting this issue as a bug in newer releases of OSMC firmware and willing to provide a fix?

6

You could try updating to the staging repository and see if it’s fixed there.

7

What is the related repo for staging?

8

Hi

Hopefully the issue is now addressed with the following commit:

I’d appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:

  1. Login via the command line
  2. Run the following command to add the staging repository:
    echo 'deb http://apt.osmc.tv bullseye-devel main' | sudo tee /etc/apt/sources.list.d/osmc-devel.list
  3. Run the following commands to update: sudo apt-get update && sudo apt-get dist-upgrade && reboot
  4. Your system should have have received the update.

Please see if the issue is resolved.

I also recommend you remove /etc/apt/sources.list.d/osmc-devel.list after updating.

This will deactivate the staging repository. You can do so with the following command:
sudo rm /etc/apt/sources.list.d/osmc-devel.list.

Please note that we will automatically disable this update channel after 14 days on your device in case you forget to do so to ensure that your system reverts to the stable update channel.

9

Hello,
many thanks for sharing these detailed instructions.

I do understand the process, however I don’t know how to revert back to a working setup once I upgraded the system from staging.

Can you please advise?

10

I assume you mean go back to stable repository. Just delete the file that you added as it is explained in the instructions.

11

Running apt-get dist-upgrade will add more than just one file.
And if I want to revert, I need to downgrade the relevant packages.
This is a lot of manual work.

12

I refereed to /etc/apt/sources.list.d/osmc-devel.list

But why do you want to revert? Just keep going from here, if you remove the repository you will be on the stable tree after the next official release.

13

Unfortunately I can’t advise further then. There’s nothing in staging that will break your system and it will be released as stable early next week.

14

I have installed staging in the meantime.
However, I can still reproduce this issue.

Please advise.

Please note that I can play another stream with staging, though.
The only difference is that the stream that fails with 404 requires user and password authentication in the URL.

15

Please upload some new logs.