mathena

I guess you guessed correctly. (At least for me. )

Thanks for testing and letting me know. :-) I'll try to work around that problem for now... I'm just wondering why nobody except for one other person ran into this problem apparently?!

Thank you for your answer! :-) I'm already doing that as otherwise the Sat>IP-Broadcasts don't reach the container...

Hi all, I'm experiencing the exact same problems: 2017-01-08 13:56:24.456 http: <my-ip>: HTTP/1.0 GET /dvrfile/3bca00ba3997378a3583ce1af366cfea -- 500 2017-01-08 13:56:24.468 http: <my-ip>: using ticket 7265BB6D3272710EA24E0794497108149CDB3050 for /dvrfile/3bca00ba3997378a3583ce1af366cfea 2017-01-08 13:56:24.468 http: <my-ip>: HTTP/1.0 GET /dvrfile/3bca00ba3997378a3583ce1af366cfea -- 500 2017-01-08 13:56:24.478 http: <my-ip>: using ticket 7265BB6D3272710EA24E0794497108149CDB3050 for /dvrfile/3bca00ba3997378a3583ce1af366cfea 2017-01-08 13:56:24.478 http: <my-ip>: HTTP/1.1 GET /dvrfile/3bca00ba3997378a3583ce1af366cfea -- 500 2017-01-08 13:56:24.490 http: <my-ip>: using ticket 7265BB6D3272710EA24E0794497108149CDB3050 for /dvrfile/3bca00ba3997378a3583ce1af366cfea 2017-01-08 13:56:24.490 http: <my-ip>: HTTP/1.0 GET /dvrfile/3bca00ba3997378a3583ce1af366cfea -- 500 2017-01-08 13:56:24.511 http: <my-ip>: using ticket 7265BB6D3272710EA24E0794497108149CDB3050 for /dvrfile3bca00ba3997378a3583ce1af366cfea 2017-01-08 13:56:24.511 http: <my-ip>: HTTP/1.0 GET /dvrfile/3bca00ba3997378a3583ce1af366cfea -- 500 2017-01-08 13:56:24.522 http: <my-ip>: using ticket 7265BB6D3272710EA24E0794497108149CDB3050 for /dvrfile/3bca00ba3997378a3583ce1af366cfea 2017-01-08 13:56:24.522 http: <my-ip>: HTTP/1.1 GET /dvrfile/3bca00ba3997378a3583ce1af366cfea -- 500 2017-01-08 13:56:24.540 http: <my-ip>: using ticket 7265BB6D3272710EA24E0794497108149CDB3050 for /dvrfile/3bca00ba3997378a3583ce1af366cfea 2017-01-08 13:56:24.540 http: <my-ip>: HTTP/1.0 GET /dvrfile/3bca00ba3997378a3583ce1af366cfea -- 500 2017-01-08 13:56:24.549 http: <my-ip>: using ticket 7265BB6D3272710EA24E0794497108149CDB3050 for /dvrfile/3bca00ba3997378a3583ce1af366cfea 2017-01-08 13:56:24.549 http: <my-ip>: HTTP/1.0 GET /dvrfile/3bca00ba3997378a3583ce1af366cfea -- 500 And so so... In fact it does not stop and goes on indefinitely. :-( I've created a docker container, I've supplied both the PUID and PGID (which are correct for the user "tvheadend" which I created). The recorded files can be watched using smb for example. Streaming of live TV is possible, without any problems. But playing a recorded file via the web page and VLC or via the Android app always fails. I've tried the docker images 44 through 47 to no avail. :-( Any hints? Best regards