lovingHDTV

Members
  • Posts

    605
  • Joined

  • Last visited

Posts posted by lovingHDTV

  1. UPDATE: I was able to restart the server, even though there were open files.  I then let it reboot, start all the dockers, manually stop Plex docker, stop array and it worked.  Not sure why Plex docker doesn't behave like everyone else, but I was able to add my new drive.

     

    I've noticed recently that my tower has issues unmounting drives.  I ran open files and the only open files are from Plex Media Server and tuner, scripts, etc, however dockers has been shutdown by the shutdown process.

     

    if I kill the plex media server process it just spawns another one.  Making it impossible for me to shut down my array, and I really need to add a new drive to it.

     

    So how do I stop plex media server after the docker service has been shutdown?  All other dockers behave perfectly, just not Plex.

     

    thanks

    david

  2. I have two subnets that I would like access to.  My LAN subnet 192.168.1.0 and AUG subnet 10.10.1.0.  Unraid is on the LAN and I can access this fine, however I cannot access the AUG subnet via wireguard.

     

    I can access it fine when I'm on my LAN.  Can this be done?

     

    For clarification:  I can ping 10.10.1.116 from the Unraid box, but I cannot get access to it via WG.

     

    thanks

    david

  3. In case this helps.  some additional routing information for nzbgetvpn. 

    sh-5.0# ifconfig
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
            inet 192.168.10.52  netmask 255.255.255.0  broadcast 192.168.10.255
            ether 02:42:c0:a8:0a:34  txqueuelen 0  (Ethernet)
            RX packets 2744  bytes 689060 (672.9 KiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 1374  bytes 799401 (780.6 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 127.0.0.1  netmask 255.0.0.0
            loop  txqueuelen 1000  (Local Loopback)
            RX packets 35  bytes 148888 (145.3 KiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 35  bytes 148888 (145.3 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
            inet 172.21.90.31  netmask 255.255.254.0  destination 172.21.90.31
            unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  (UNSPEC)
            RX packets 12  bytes 950 (950.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 12  bytes 852 (852.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    sh-5.0# iptables --list
    Chain INPUT (policy DROP)
    target     prot opt source               destination         
    ACCEPT     all  --  anywhere             anywhere            
    ACCEPT     all  --  192.168.10.0/24      192.168.10.0/24     
    ACCEPT     udp  --  anywhere             anywhere             udp spt:openvpn
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:radg
    ACCEPT     tcp  --  anywhere             anywhere             tcp spt:radg
    ACCEPT     tcp  --  192.168.10.0/24      anywhere             tcp dpt:radg
    ACCEPT     icmp --  anywhere             anywhere             icmp echo-reply
    ACCEPT     all  --  anywhere             anywhere            
    
    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination         
    
    Chain OUTPUT (policy DROP)
    target     prot opt source               destination         
    ACCEPT     all  --  anywhere             anywhere            
    ACCEPT     all  --  192.168.10.0/24      192.168.10.0/24     
    ACCEPT     udp  --  anywhere             anywhere             udp dpt:openvpn
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:radg
    ACCEPT     tcp  --  anywhere             anywhere             tcp spt:radg
    ACCEPT     tcp  --  anywhere             192.168.10.0/24      tcp spt:radg
    ACCEPT     icmp --  anywhere             anywhere             icmp echo-request
    ACCEPT     all  --  anywhere             anywhere            

     

  4. Played a bit more.

     

    1. installed linuxserver nzbget (as it doesn't integrate VPN).  This worked fine.

     

    2. with nzbgetvpn - I can ping it, but if I do a curl command it times out

    I can successfully run the curl command from my PC on the 192.168.1.0/24 subnet so my router is routing to the docker.

     

    I cannot ping the br0.10 docker from a tower command prompt.  The tower is on the 192.168.1.0/24 subnet also.

     

    something is amiss and I can't figure it out.

     

    david

  5. Ok, set it back up.

     

    I can ping plex and can notify plex, so I was mistaken there.  I then tried nzbgetvpn and delugevpn and I can ping them also, but cannot connect.

     

    It is making me wonder if the routing within the docker is handling the LAN setting correctly.

     

    Here are the routes in delugevpn, they look OK to me, but I'm not an expert:

    sh-5.0# route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         172.21.90.1     128.0.0.0       UG    0      0        0 tun0
    0.0.0.0         192.168.10.1    0.0.0.0         UG    0      0        0 eth0
    128.0.0.0       172.21.90.1     128.0.0.0       UG    0      0        0 tun0
    172.21.90.0     0.0.0.0         255.255.254.0   U     0      0        0 tun0
    173.245.203.252 192.168.10.1    255.255.255.255 UGH   0      0        0 eth0
    192.168.10.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0

    Here they are in sonarr:

    sh-5.0# route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         192.168.10.1    0.0.0.0         UG    0      0        0 eth0
    192.168.10.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0

    routes for nzbget when on bridge: (this works with Sonarr on bridge)

    sh-5.0# route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         172.21.90.1     128.0.0.0       UG    0      0        0 tun0
    0.0.0.0         172.17.0.1      0.0.0.0         UG    0      0        0 eth0
    128.0.0.0       172.21.90.1     128.0.0.0       UG    0      0        0 tun0
    172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 eth0
    172.21.90.0     0.0.0.0         255.255.254.0   U     0      0        0 tun0
    192.168.1.0     172.17.0.1      255.255.255.0   UG    0      0        0 eth0
    209.197.16.148  172.17.0.1      255.255.255.255 UGH   0      0        0 eth0

     

  6. Yes, in sonarr for example, I change Plex's IP to the new one for notifications.  I hit test and it cannot find plex.  I moved it all back, change all the IPs in docker and applications and it works.  Which is why I statically set the IP in the docker setup, so I know how to set them in each application.

     

    david

  7. Today I have several dockers on br0.10 including plex and emby.  I have several dockers on bridge, including deluge, nzbget, sonarr, couch potato.

     

    I would like to move the dockers from bridge to br0.10.  When I do this, they kind of work.  I can get to their web interfaces, they can get to the internet, but sonarr cannot get to deluge or nzb.  I can open a bash in the sonarr docker and ping the br0.10 ip for deluge, but for whatever reason sonarr cannot find deluge.  This obviously breaks everything.

     

    Is there something I have to do differently with the br0.10 setup to get this to work?  Currently I have plex and emby on br0.10 because that is the vlan my TV/nvidia shild is on and it makes network traffic a bit better.  However, sonarr and couch potato cannot notify them of updates as they are on bridge.

     

    Is this even possible?  Does my question make sense?

     

    thanks

    david

  8. For a specific question.

     

    I have the  <WebUI>http://[IP]:[PORT:80]/</WebUI>  set in my template.xml, but when I click on the Docker Icon I  only see _console, no WebUI option.  The webserver is running and I can connect to it.  Is there something else I need to add to get the WebUI option for the context sensitive menu?

     

    thanks

    david

  9. gotify looks really interesting.  I was able to run its docker command and it ran, though I have no idea what happens under the hood of UnRaid.  It appears in the docker page under some name.

     

    I think this is a very interesting piece of the solution.

     

    Still interested in documentation on how to make an UnRaid compatible dockerfile/xml.

     

    EDIT: https://wiki.unraid.net/index.php/DockerTemplateSchema

     

    david

  10. I just started using a Hubitat Elevation for my home automation.  They dropped SMS support for Twilio, but someone created a nice add-on to restore this functionality.  It needs a linux (most people use an rPi) with node-js, npm and sendmail installed.

     

    https://github.com/adsavia/Hubitat-DoNS

     

    I'd like to make a docker so that I can run this service on my UnRaid box, but really have no idea how to go about it.  I thought there was a post here somewhere that taught you how to do this.  Any pointers/help much appreciated.

     

    thanks

    david

  11. 17 hours ago, lovingHDTV said:

    Further playing.

     

    In the log file it says: 

    
    19-12-13 19:34:59.1|Warn|SkyHookProxy|The operation has timed out.: 'http://skyhook.sonarr.tv/v1/tvdb/search/en/?term=magnum pi'

    When I put that in my browser, sure enough it times out, but if I put https:// then it works fine.

     

    Can I change this from http to https anywhere in the settings? I didn't see it anywhere obvious.

     

    david

     

    Ok not an issue with Sonarr.  Everything works fine if I run through a VPN, or if I setup Sonarr on br.10 or br.20.  I think it is something wrong with my new ISP.

     

    david

  12. 1 hour ago, lovingHDTV said:

    I played around a bit more, and found that if I move it to the br.10 it can find new shows.  I then tried br.0 and assigned it an IP, and that doesn't work.

     

    I'm running Version: 6.8.0-rc4, could that be the issue?  I know there is an outstanding bug on dockers/vm/ips etc.

     

    david

    Further playing.

     

    In the log file it says: 

    19-12-13 19:34:59.1|Warn|SkyHookProxy|The operation has timed out.: 'http://skyhook.sonarr.tv/v1/tvdb/search/en/?term=magnum pi'

    When I put that in my browser, sure enough it times out, but if I put https:// then it works fine.

     

    Can I change this from http to https anywhere in the settings? I didn't see it anywhere obvious.

     

    david

     

  13. On 12/10/2019 at 9:11 PM, lovingHDTV said:

    when I try to add a new series it just spins and eventually times out.  This worked a couple weeks ago and I don't think I changed anything.  I can go to tvdb and search successfully .  I tried to search for the tvdbid and that doesn't work either.

     

    Any ideas?

     

    thanks

    david

    I played around a bit more, and found that if I move it to the br.10 it can find new shows.  I then tried br.0 and assigned it an IP, and that doesn't work.

     

    I'm running Version: 6.8.0-rc4, could that be the issue?  I know there is an outstanding bug on dockers/vm/ips etc.

     

    david

  14. when I try to add a new series it just spins and eventually times out.  This worked a couple weeks ago and I don't think I changed anything.  I can go to tvdb and search successfully .  I tried to search for the tvdbid and that doesn't work either.

     

    Any ideas?

     

    thanks

    david

  15. I'm trying to move all my dockers to my IOT vlan.  I've successfully moved plex, deluge and nzbget.  I can access them via their web interfaces fine.  I also moved Sonarr and can access its web interface fine.  However I cannot get Sonarr to connect to either of the downloaders.  I did update the ips to the new ips, they are all on the same subnet.

     

    I opened a console into the Sonarr docker and can ping the IPs for the two download clients.  

     

    Any ideas what I need to do to get Sonarr to be able to connect to the download clients?  Essentially I've moved everything from bridge to br0.10.

     

    One additional comment: it connects to jackett just fine after I moved jackett as well.

     

    thanks

    david

  16. 3 hours ago, itimpi said:

    There is no need to have a file anywhere near that big.    The default size of 1GB is probably far more than is needed as all that is stored inside it is configuration information about the VM service and any VMs you create.

    Ok how do I change that?  I don't see that option in the VM settings any longer. I do see the btrfs as 20GB.

     

    NM figured it out