Mylo75
-
Posts
83 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Mylo75
-
-
Yes, completely deleted all previous versions and files of previous installs. Even threw in a system reboot for good measure.
Maybe I should try the unRAID DVB Edition?
-
12 hours ago, saarg said:
And you are using host mode?
Yes in host mode.
-
4 hours ago, saarg said:
I have almost no knowledge of the hdhomerun, but since it sees it I guess you already run the container in host mode?
Have you tried both the stable and latest version of tvheadend?
Yea I have tried all 3 options when installing linuxserver tvheadend docker, but always end up with the same result no DVB-T tuners found. Very strange.
-
I do not have the unRAID DVB Edition installed as the first page on that thread says hdhomerun tuners will work without this special unraid version installed.
I am using an hdhomerun tuner but my tvheadend docker will only find the dvb-c tuners, no dvb-t tuners are listed.
Whereas using tvheadend from my libreelec vm all tuners are found and working correctly.
Any thoughts or suggestions.
Thanks.
-
I do not have unRAID DVB Edition installed as the first page here says hdhomerun tuners will work without this special unraid version installed.
I am using an hdhomerun tuner but my tvheadend docker will only find the dvb-c tuners, no dvb-t tuners are listed.
Whereas using tvheadend from my libreelec vm all tuners are found and working correctly.
Any thoughts or suggestions.
Thanks.
-
Thanks Bungy, I'll have another bash at it myself (it's a good way for me to learn all this stuff), if I'm still having problems I'll get back to you. Cheers.
-
No joy. This is from the nzbgetvpn log
2017-04-11 14:54:50,226 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 6789 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 6789 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 6789 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 6789 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
2017-04-11 14:54:50,226 DEBG 'start-script' stdout output:
--------------------
[info] Starting OpenVPN...
2017-04-11 14:54:50,231 DEBG 'start-script' stdout output:
Tue Apr 11 14:54:50 2017 OpenVPN 2.3.11 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on May 12 2016
Tue Apr 11 14:54:50 2017 library versions: OpenSSL 1.0.2h 3 May 2016, LZO 2.09
Tue Apr 11 14:54:50 2017 WARNING: file 'credentials.conf' is group or others accessible
2017-04-11 14:54:50,252 DEBG 'start-script' stdout output:
Tue Apr 11 14:54:50 2017 UDPv4 link local: [undef]
Tue Apr 11 14:54:50 2017 UDPv4 link remote: [AF_INET]213.120.234.114:1198
2017-04-11 14:54:51,253 INFO success: nzbget entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) -
You mean my "tower" ip address, or default gateway
Network mask:
255.255.255.0
-
See pics attached as previous post didn't post correctly.
-
Bump. Is this docker no longer supported?
-
WARNING: file 'credentials.conf' is group or others accessible
I get the above error (the only error) in the log when trying to run nzbgetvpn,
This site can’t be reached when i try to access the gui.
If i set to "no" in " Container Variable: VPN_ENABLED " I can access the gui and this docker works fine.
Any help appreciated, let me know if more info needed.
-
23 hours ago, Squid said:
I had thought about adding in a utility to delete them all when the bug was discovered, but decided against it because for all I know those files named Squidbait* might actually belong on your array for your own purposes, and the last thing I wanted to do was inadvertently delete your own files.
The latter versions tell you about creation errors (if you have the bait files set to be recreated), and clicking the link brings up a list of where the stragglers left from prior versions are... A straggler is a file that as far as RP is concerned belongs on the array because it is a pre-existing file named the same. IE: If you do have a file of your own named Squidbait*, then RP will not overwrite it, nor will it monitor it for changes)
Wasn't having a go at you Squid, just in case you thought that. 2 mins got rid of the stragglers, made all shares public, went to Windows Explorer on my desktop, searched for Squid and sapped them.
-
6 hours ago, trurl said:
It's a plugin, not a docker. Very different things.
Yea my mistake, I was tired deleting all those wee Squid files
-
Ah Squid that sounds correct " version on the plugin that had a bug within it, and the system didn't keep track of them."
Its a painful process going through each share and folder/sub folder to delete these
Windows explorer, all shares public, search and delete got it now.
Thanks for this docker btw.
-
So I installed this docker and have been fiddling about with it. Before uninstalling I clicked the "delete previous bait files" to remove all the bait files. After uninstalling there are still a load of these squidbait files in all my folders. Is there anyway i delete these all in one go. Thanks
-
Just a few questions, from a noob with no command line knowledge.
So I've got this set up with sonarr, cp, nzbget etc.. working with [email protected] and have it password protected.
My Web address is https://[email protected] adding /nzbget or /sonarr etc... at the end.
Is this correct and have I set up it all properly, or should it be https://sonarr.mydomain.duckdns.org
Also by running my dockers through letsencrypt, does this give them better security when they connect to the Internet or is the security just for me when I connect to them from a different network.
Do I still need to enable ssl and proxy settings in each docker as well for better security.
Basically I want the best security I can get for my nzbget, so any help, hints or tips much appreciated.
-
Thanks John. Yes I think that explains it as I added a new cache drive and moved my docker image from another disk (which must have been btrfs)
So I will delete docker image and start new docker from scratch.
-
This is from my log, I have no btrfs formatted disks. So why all these errors all of a sudden. Thanks.
Also what is this? Feb 13 17:12:32 Tower root: plugin: running: anonymous
Feb 13 17:08:00 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:00 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:00 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:04 Tower kernel: __readpage_endio_check: 64 callbacks suppressed
Feb 13 17:08:04 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:04 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:04 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:04 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:04 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:04 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:04 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:04 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:04 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:05 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:20 Tower kernel: __readpage_endio_check: 26 callbacks suppressed
Feb 13 17:08:20 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:08:20 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:09:13 Tower root: Fix Common Problems Version 2017.02.03b
Feb 13 17:09:17 Tower root: Fix Common Problems Version 2017.02.03b
Feb 13 17:09:43 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin checkall
Feb 13 17:10:07 Tower root: Fix Common Problems Version 2017.02.03b
Feb 13 17:11:05 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:12:32 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove fix.common.problems.plg
Feb 13 17:12:32 Tower root: plugin: running: anonymous
Feb 13 17:14:43 Tower emhttp: shcmd (588): smbcontrol smbd close-share 'Movies'
Feb 13 17:17:02 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 17:19:42 Tower emhttp: shcmd (781): smbcontrol smbd close-share 'flash'
Feb 13 17:21:26 Tower emhttp: shcmd (846): smbcontrol smbd close-share 'flash'
Feb 13 17:22:46 Tower kernel: kvm: already loaded the other module
Feb 13 18:17:01 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 19:17:02 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 20:17:01 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 20:26:03 Tower rpc.mountd[4238]: authenticated mount request from 192.168.1.124:35815 for /mnt/user/TV Shows (/mnt/user/TV Shows)
Feb 13 21:17:02 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
Feb 13 22:17:01 Tower kernel: BTRFS warning (device loop0): csum failed ino 20234 off 148578304 csum 1439286410 expected csum 2378018366
-
The funny thing is we had a power cut last night (I have a ups connected) so the server did reboot.
Thanks for helping.
-
OK now working.
Had to remove tvheadend docker completely and reboot.
Install tvheadend docker and reboot again.
All the things I should have done first I guess.
-
Thanks for your help, I'll get a chance to troubleshoot more later.
-
August DVB-T210 - HD Freeview USB TV Tuner - External DVB-T2 Digital Television Receiver and PVR Style Recorder
It worked on this dvb build before the tvheadend docker image updated a few days ago.
-
See my above post
-
[Support] Linuxserver.io - TVHeadend
in Docker Containers
Posted
After much googling solution discovered
https://tvheadend.org/boards/5/topics/24870?r=24877#message-24877
This might be good info to put somewhere for future users to see.