docker-get_iplayer icon indicating copy to clipboard operation
docker-get_iplayer copied to clipboard

Errors when downloaded - New version required?

Open ProjectVRD opened this issue 3 years ago • 2 comments

The following errors occur when the PVR runs since June 7th\8th, does the get_iplayer version need to be updated?

ERROR: Failed to download URL (3/3): https://c1b1bteaips.sp.bidi.live.bbc.co.uk/vod-hls-uk/usp/auth/vod/piff_abr_full_hd/fd6824-m000wvpf/vf_m000wvpf_7d34e446-ca9e-4775-ae01-e7fb14d01021.ism.hlsv2.ism/iptv_hd_abr_v1_hls_master.m3u8?at=HDEiM0hjd20f6969eb549f71876ea66ef540d0aaa51bb6d15c45c28607a40 ERROR: Response: 403 Forbidden ERROR: Access to this resource was blocked by the BBC ERROR: Ignore this error if programme download is successful

WARNING: A UK TV licence is required to access BBC iPlayer TV content legally INFO: Downloading tv: 'Episode details'

INFO: Downloaded: 0.00 MB (00:00:00) @ 0.00 Mb/s (hvfhd1/bi) [audio+video] WARNING: Unexpected size for file segment [1] WARNING: Expected: 5044792 Downloaded: 31667 WARNING: This indicates a problem with your network connection to the media server

ProjectVRD avatar Jun 09 '21 21:06 ProjectVRD

Try using a VPN when you are outside the UK.

The get_iplayer version is updated daily in the background, so this should not be the problem.

A full re-build of the container didn't fix it for me, only using it through a VPN did.

mgoeppl avatar Sep 21 '21 18:09 mgoeppl

I've also been experiencing these errors since about that time, I am in the UK so don't need the VPN. My experience is eventually the programmes do download but it may take some days after they are available. I thought this was just how things were working right now. Often the thumbnails are corrupt, and files downloaded that used to be removed remain, such as *.ts, *.jpg and others.

Indexing produces many 403 errors:

ERROR: Failed to download BBC Radio London schedule page (3/3): https://www.bbc.co.uk/schedules/p00fzl6f/2021/w50 ERROR: Connection error: Invalid argument ............................................................. INFO: Indexing radio programmes (concurrent) [future] ERROR: Failed to download BBC Radio 1Xtra schedule page (3/3): https://www.bbc.co.uk/schedules/p00fzl64/2021/w50 ERROR: Connection error: Invalid argument ERROR: Failed to download BBC Radio 1Xtra schedule page (3/3): https://www.bbc.co.uk/schedules/p00fzl64/2021/w51 ERROR: Connection error: Invalid argument

PVR produces 500 errors:

WARNING: Response: 500 Status read failed: Invalid argument WARNING: Ignore this warning if programme download is successful WARNING: Failed to download URL (2/3): https://www.bbc.co.uk/iplayer/episode/m0012lbm/sign WARNING: Response: 500 Status read failed: Invalid argument WARNING: Ignore this warning if programme download is successful WARNING: Failed to download URL (3/3): https://www.bbc.co.uk/iplayer/episode/m0012lbm/sign WARNING: Response: 500 Status read failed: Invalid argument WARNING: Ignore this warning if programme download is successful

A manual run often produces the transfer errors as mentioned above:

WARNING: Unexpected size for file segment [1] WARNING: Expected: 62556 Downloaded: 15364 WARNING: This indicates a problem with your network connection to the media server WARNING: Retrying tv: 'Doctors: Series 22 - 125. For Richer, for Poorer (m0012k33) [original]' WARNING: Unexpected resume data: 0,637,0,637,0,1639744269 WARNING: Restarting download ################################################################################ INFO: Downloaded: 27.13 MB (00:27:54) @ 24.12 Mb/s (dvfxsd2/bi) [audio]

I installed a different docker build for get_iplayer, this runs fine using the same configuration files from /output/.get_iplayer and the checksums are identical for get_iplayer on both. It also runs fine from those files when installed on my Mac (no docker build).

Also tried fresh download/relaunch marginal/get_iplayer, updated perl and AtomicParsley within, apk upgrade | apk update

The errors mention network, but a parallel docker on the same machine works fine and a speed test from the docker build was able to do line speed 73Mbit/s so I doubt it's that. I don't see a firewall in the build that could be in the way and I have checked and compared dockers settings between the two builds.

I'm at the limit of my knowledge. I would love to get it going again, the build is so compact and simple.

Has anyone found a solution or can think of what's not right here?

slimgym avatar Dec 17 '21 13:12 slimgym