Monkeyair

Air Video HD Anyone know how to firm up a Server Pin for remote access? I'd like to stop the docker from generating new PIN's that stop me accessing the server remotely. Thanks.

Ok, I've sorted it now thanks. I deleted the docker, reinstalled it and added the OpenVPN files again. Seems to have done the trick this time. I'm back up and running again.

As from this morning my SABnzbdVPN docker no longer works. I didn't change anything and am wondering if I now need to make changes due to the update? I have automatic updates enabled. This is the docker log: I tried reinstalling the OpenVPN file from Torguard, but it did not help. Any ideas?

I have gone back to 6.2.1 and all works again...

I've had the same issue upgrading to 6.3.0. I am running a Nvidia GT720. The VM works when run with a VNC but not when the GPU is selected on the template. I tried the old "options snd-hda-intel enable_msi=1" but no joy. Any ideas on this? This setup worked fine until I upgraded.....

Yes Neil. In the preferences of the MKV programme, you have to change the completed destination folder otherwise the docker image fills up... I did this, but failed to notice that it was reverting back again after restart. A reinstall of the docker seemed to solve it

Some dirty buggers will nick anything!

Did I not tell you? This one's yours:

Cheers Saarg I may do a bit of research then

That 's tickled me..... Has anyone ever tried to get Sky TV working in the UK with the OMNIKEY 3121, Oscam and TVHeadend? Just wondered if it was still possible to do with the updates to encryption........

I shall visit CHBMB's Shrine and make a suitable donation to the media God

How big is the update? Because mine is constantly showing an update available but when I update it, it's the grand total of 0 bytes. The "update" may not be the cause of your problems. Hi Neil Guess who forgot to put the "--device=/dev/dvb" into the extra parameters of the unstable docker after reinstalling? You're right again mate. It wasn't the phantom update, it was me being a nugget! Sniper told you that we all have our moments So now I'll just ignore the "Update available" and get on enjoying my setup. Cheers

Hi Saarg I'm having a problem with an update to the TVHeadend Unstable Docker. I have an update available showing that keeps returning even after updating. If I do the update the system becomes somewhat unstable, with the sound becoming intermittent or even unavailable. If I then delete the docker and reinstall it, all works well, but with an update available showing. Any ideas? Thanks

The pulse eight adapter works perfectly with the VM. We've all made the same mistakes lol

Your setting in tvheadend needs to be /recordings The same as your path in the docker settings. Hope that helps

ThEg have you checked to see if there is something that is filling up your docker image?

Sniper can you post a screenshot of your docker settings and the recorder path in tvheadened.....

I have no lag with cards and responsiveness is excellent. I changed one of my DVB-T cards for the DVB-S version. The spare card is due to go on eBay soon......

Hi ThEgOg I too am in the UK and run my server with a LibreELEC VM. The TVheadend server runs two TBS cards and distributes the TV to several Raspi 2's around the house. I too had issues with a DVBSky tuner and returned it to Amazon for a refund. After swapping and changing, I finally ended up with the TBS 6904 and a TBS 6205. They work perfectly and I would certainly recommend them with the TBS media build. Hope that helps

LibreElec VM. It's there all ready to go. Get on it

This has been resolved. It was an error in the MKV docker setup.

Zan as far as I know, the skip commercials does not work. Neil, I'm on the Sutton Coldfield transmitter and I think that we are using the same DVB cards too. After forcing the scan status to active a few times I can get all of the muxes apart from 514mhz. I assume that is one of the ones that you can't get as it's not even listed on Free-TV site.

Since upgrading to 6.2.0 beta I have had no end of problems with my docker image filling up. I added this command to all of my dockers to restrict the size of the logs: --log-opt max-size=50m --log-opt max-file=1 This command showed this had been a suucess: du -ah /var/lib/docker/containers/ | grep -v "/$" | sort -rh | head -60 I woke this morning to see the server had issued warnings about the docker size. It had been growing by 1% every minute or so until it became 100% full and fell over. This is not now due to logs, but something else. I have deleted the docker image and restarted with a fresh img. I shall try and find the culprit with Cadvisor. Any ideas how I can find the solution to this?

The new update solved it. Thanks Saarg Oh and Neil.

Since the update 3 muxes now show as failed. I wonder if this is the reason why the log was going mental? I'll try another docker version and see if it fixes it. The log seems to be under control now thanks.