I rebooted the K-III Pro box for good luck and checked that the IP address of the box was 192.168.0.8. I then got into that K-III Pro box, and reset the IP Address Method to DHCP. I got Into the router and reserved IP address 192.168.0.8 for the MAC address of one of my K-III Pro boxes. Ok, I had to check the second scenario you described above. IMO, it is preferable to set the static IPs on the router. So if you select a static IP on the box, you need to specify that IP in the settings.īut if you set the static IP on the router and use DHCP to get that IP on the box, then localhost/127. I’m sure that some others will fall into the same traps that I’ve fallen into, so I’m hoping that this thread may be useful. I’ve been struggling with them for a couple of months now. To be honest with you, I’m just happy that both boxes now work. I think a skilled network guy could probably steer me in the right direction. It did this when only one box was powered up and configured, and it does exactly the same thing when both boxes are powered up and configured. 127.0.0.1 then I have no connection and I can’t watch TV. If I leave the default setting on the TVH client, i.e. I could probably cross over the client and server combination if I wanted to. The only way I can connect the TVH HTSP Client to it’s respective server, is by telling it the static IP address of the box (and hence the address of that TVH Server). I’ve got two K-III Pro boxes each with it’s own static IP address. I usually only use DHCP for mobile phones etc.įor most of my other devices I like to use static IP addresses. I didn’t actually test the second scenario. I don’t claim to fully understand why or how it works.
Just bare in mind that this fix is effective in my network environment, and there is no guarantee that it will work for you. I’m basically raising this posting in case it may help others who might have the same problem. On the other hand if I set this IP address to the default 127.0.0.1 it would instantly stop working. I found that whilst configuring the Tvheadend HTSP Client, if I set the Tvheadend hostname or IP address, to 192.108.1.7 then Tvheadend would spring to life, and I’d be watching TV. Now to get to the point, when setting up CoreELEC I chose to give it a static IP address of 192.108.1.7 After 3 nights of hacking I have finally stumbled across the reason for the Access Denied messages and Tvheadend now works like an out of the box product. I would immediately get the Access Denied messages. After booting up CoreELEC, I installed from the CoreELEC add-ons repository the Tvheadend service and client add-ons. I’m currently using a K-III Pro, and I loaded 8.95.1 onto an SD card. I think I might have a fix, or at least a workaround.įirst I’ll give you a heads up on my setup. Hi guys, I’ve been eagerly waiting for the latest CoreELEC 8.95.1, hoping that it would fix issues I’ve been having with Tvheadend not working since about release 8.90.3.
0 kommentar(er)
