[Support] Linuxserver.io - TVHeadend


Recommended Posts

Hey Page3,

 

the correct URL should be

 

http://IP:9981/play/dvrfile/

My apologies, I was writing from memory. You're correct, path is:

 

http://192.168.0.50:9981/play/dvrfile/608a2e04cd8e247011db29e9f90044ef (with or without a title parameter).

Any firewalls/anti-virus software that might interfere?

No, afraid not. Playing locally. Mac (so no antivirus).

 

Playback fails on Mac, iPad and AppleTV.

Live TV works fine from all three.

Playback works fine if I network browse to the .ts file directly on all of the devices.

 

BTW, just tried http://192.168.0.50:9981/playlist/channels  from VLC and that works fine.

Link to comment

Hey Page3,

 

the correct URL should be

 

http://IP:9981/play/dvrfile/

My apologies, I was writing from memory. You're correct, path is:

 

http://192.168.0.50:9981/play/dvrfile/608a2e04cd8e247011db29e9f90044ef (with or without a title parameter).

Any firewalls/anti-virus software that might interfere?

No, afraid not. Playing locally. Mac (so no antivirus).

 

Playback fails on Mac, iPad and AppleTV.

Live TV works fine from all three.

Playback works fine if I network browse to the .ts file directly on all of the devices.

 

BTW, just tried http://192.168.0.50:9981/playlist/channels  from VLC and that works fine.

 

It works correctly here. When I click the play button it downloads a m3u file with the link. If I open that one in VLC it starts playing. If I copy the link address on the play button it also works, but then asks for a username/password.

 

Does your users have the right permissions?

Did you add a new user and delete the default one?

 

Didn't see your edit about it working in VLC. So then it's a matter of using the correct address/way to play the recordings.

Link to comment

Hey Page3,

 

the correct URL should be

 

http://IP:9981/play/dvrfile/

My apologies, I was writing from memory. You're correct, path is:

 

http://192.168.0.50:9981/play/dvrfile/608a2e04cd8e247011db29e9f90044ef (with or without a title parameter).

Any firewalls/anti-virus software that might interfere?

No, afraid not. Playing locally. Mac (so no antivirus).

 

Playback fails on Mac, iPad and AppleTV.

Live TV works fine from all three.

Playback works fine if I network browse to the .ts file directly on all of the devices.

 

BTW, just tried http://192.168.0.50:9981/playlist/channels  from VLC and that works fine.

 

It works correctly here. When I click the play button it downloads a m3u file with the link. If I open that one in VLC it starts playing. If I copy the link address on the play button it also works, but then asks for a username/password.

 

Does your users have the right permissions?

Did you add a new user and delete the default one?

 

Didn't see your edit about it working in VLC. So then it's a matter of using the correct address/way to play the recordings.

Glad to hear it works. At least it means I must be doing something wrong.

 

It's strange that I can play live tv fine via the web interface and vlc, but just not any recordings. If I click on the play icon within the interface, or use the URL within vlc (on any device) I get nothing except not found.

 

I'm using the default user, which I believe has correct permissions. This gives me something new to try though - good idea.

 

Regards.

Link to comment

Hey Page3,

 

the correct URL should be

 

http://IP:9981/play/dvrfile/

My apologies, I was writing from memory. You're correct, path is:

 

http://192.168.0.50:9981/play/dvrfile/608a2e04cd8e247011db29e9f90044ef (with or without a title parameter).

Any firewalls/anti-virus software that might interfere?

No, afraid not. Playing locally. Mac (so no antivirus).

 

Playback fails on Mac, iPad and AppleTV.

Live TV works fine from all three.

Playback works fine if I network browse to the .ts file directly on all of the devices.

 

BTW, just tried http://192.168.0.50:9981/playlist/channels  from VLC and that works fine.

 

It works correctly here. When I click the play button it downloads a m3u file with the link. If I open that one in VLC it starts playing. If I copy the link address on the play button it also works, but then asks for a username/password.

 

Does your users have the right permissions?

Did you add a new user and delete the default one?

 

Didn't see your edit about it working in VLC. So then it's a matter of using the correct address/way to play the recordings.

Glad to hear it works. At least it means I must be doing something wrong.

 

It's strange that I can play live tv fine via the web interface and vlc, but just not any recordings. If I click on the play icon within the interface, or use the URL within vlc (on any device) I get nothing except not found.

 

I'm using the default user, which I believe has correct permissions. This gives me something new to try though - good idea.

 

Regards.

 

Just read your edit again and its live TV you talk about working  :)

Do you use the IP or the name of your server?

 

Do not use the default user! Its only there to login and make new users. If you used the wizard and added users, those are OK, but the * user should not be used. It cases problems, probably your problem now.

Link to comment

I've tried adding two new users and giving them appropriate access rights. Unfortunately it hasn't helped.

 

Neither of these work from the browser, VLC or TVHClient on the iPad. Nor does the Play or download link from the UI.

 

http://user:[email protected]:9981/play/dvrfile/285e44ecf0ea44432f7e996cce82fd91

http://user:[email protected]:9981/dvrfile/285e44ecf0ea44432f7e996cce82fd91

 

I've spent hours and hours on this and am beginning to give up to be honest. :(

Link to comment

I've tried adding two new users and giving them appropriate access rights. Unfortunately it hasn't helped.

 

Neither of these work from the browser, VLC or TVHClient on the iPad. Nor does the Play or download link from the UI.

 

http://user:[email protected]:9981/play/dvrfile/285e44ecf0ea44432f7e996cce82fd91

http://user:[email protected]:9981/dvrfile/285e44ecf0ea44432f7e996cce82fd91

 

I've spent hours and hours on this and am beginning to give up to be honest. :(

 

What does the tvheadend log say? Click arrow button in the bottom right corner of the webui and the log window should open. Then try to play a recording and see what pops up in the log.

Link to comment

What does the tvheadend log say? Click arrow button in the bottom right corner of the webui and the log window should open. Then try to play a recording and see what pops up in the log.

2016-12-24 13:34:19.724 http: 192.168.0.21: HTTP/1.1 GET /dvrfile/285e44ecf0ea44432f7e996cce82fd91 -- 500

 

Thanks for all your help so far :)

Link to comment
  • 2 weeks later...

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

Link to comment

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

 

This looks like a bug in tvheadend. I get the same problem here when testing. You can either wait and hope it gets fixed, or submit a bug report on the tvheadend site.

Link to comment

please help im trying to set up with a HDHome run connect, this is a DVB-T, T2 tuner.

 

the problem is tvheadend detects it as a DVB-C tuner, therefore not allowing b

me to assign the correct DVB-T network to it.

 

any help would be appreciated

 

Sorry, but I have no experience with hdhomerun. You might try the tvheadend forum.

Link to comment

Hi, may here someone has an idea why my twin tuner card may doesnt work properly

 

i have two hauppage WinTV-HVR-5500, a DVB C, S, S2, ... card.

 

in UNRaid DVB the cards are shown like this

 

DVB Kernel: Detected

DVB Adapter Drivers: Detected

DVB Adapter 0: NXP TDA10071

DVB Adapter 1: Silicon Labs Si2165 DVB-T DVB-C

DVB Adapter 2: NXP TDA10071

DVB Adapter 3: Silicon Labs Si2165 DVB-T DVB-C

 

so i assume adapter 0+1 = card 1, adapter 2+3 = card 2.

 

adapter 0+2 (DVB S) are working fine, adapter 1 + 3 (DVB C) are not working properly, recognized in TVH, i can config them and so on,

but scanning always fail like this

 

2017-01-13 06:46:35.408 mpegts: 114MHz in DVB-C Netzwerk - tuning on Silicon Labs Si2165 DVB-T DVB-C : DVB-C #0

2017-01-13 06:46:35.408 subscription: 01BB: "scan" subscribing to mux "114MHz", weight: 6, adapter: "Silicon Labs Si2165 DVB-T DVB-C : DVB-C #0", network: "DVB-C Netzwerk", service: "Raw PID Subscription"

2017-01-13 06:46:35.471 linuxdvb: Unable to provide signal strength value.

2017-01-13 06:46:35.471 linuxdvb: Unable to provide BER value.

2017-01-13 06:46:35.471 linuxdvb: Unable to provide SNR value.

2017-01-13 06:46:35.471 linuxdvb: Unable to provide UNC value.

2017-01-13 06:46:40.408 mpegts: 114MHz in DVB-C Netzwerk - scan no data, failed

2017-01-13 06:46:40.408 subscription: 01BB: "scan" unsubscribing

2017-01-13 06:46:40.408 mpegts: 130MHz in DVB-C Netzwerk - tuning on Silicon Labs Si2165 DVB-T DVB-C : DVB-C #0

2017-01-13 06:46:40.408 subscription: 01BD: "scan" subscribing to mux "130MHz", weight: 6, adapter: "Silicon Labs Si2165 DVB-T DVB-C : DVB-C #0", network: "DVB-C Netzwerk", service: "Raw PID Subscription"

2017-01-13 06:46:45.408 mpegts: 130MHz in DVB-C Netzwerk - scan no data, failed

2017-01-13 06:46:45.408 subscription: 01BD: "scan" unsubscribing

...

from the system log in unraid

Jan 13 06:46:26 AlsServer kernel: cx23885 0000:05:00.0: Direct firmware load for dvb-demod-si2165.fw failed with error -2

Jan 13 06:46:26 AlsServer kernel: i2c i2c-4: si2165: firmware file 'dvb-demod-si2165.fw' not found

 

i assume its about the twin tuners not accepted correctly or some config ?

 

both cards worked before nice on Windows using Mediaportal as Backend, but as im testing here on unraid now and really like it i try figuring what could be the reason ..

 

DVB-S all nice as it should, also with SAT-IP server etc etc ...

 

may an idea ? any more infos needed to investigate ?

Link to comment

Hello,

 

i've updated the docker image today and now most of my settings are gone. channels, ca, language etc etc. the only thing remaining is the autorec and records-tabs

do i have to change anything to remain settings for an update or is this behavior expected?

Link to comment

Hello,

 

i've updated the docker image today and now most of my settings are gone. channels, ca, language etc etc. the only thing remaining is the autorec and records-tabs

do i have to change anything to remain settings for an update or is this behavior expected?

 

It's not normal that you loose the settings, but it might happen when you use the development branch. If you want the stable release, you don't risk it.

 

When tvheadend updates it stores a backup of the old config on the first run, so chances are you still have your old config. Or it might also be a bug in tvheadend, but not that likely. I can't check anything until I get back from work today, but please supply the logs from tvheadend. The below command should show the logs.

 

docker logs tvheadend

Link to comment

Hello guys.

 

Im trying to set the http_url argument for this docker, i have tried and edit /var/run/s6/services/tvheadend/run and adding the following argument --http_root /tv

But everytime i restart the container the run file is reset back to default.

 

Is there any way that i can modify this without it resetting

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.