Jump to content

Jcloud

Members
  • Joined

  • Last visited

  1. Information and method is appreciated, but could we please get the instructions also be provided in text form, so as not to sit/skip through 11min video? More of a general request/observation w/ Spaceinvader post(s) in general.
  2. Was bored, saw your post did some digging. I've never passed a device to a docker before, or used SageTV Containers, but found other containers which have done this -- I figure it's got to be similar. From a Docker command line perspective I think you want to use your system's equivalent to: --device=/dev/dvb \ From a generic Docker template stand-point I think you're wanting to "add device" to Docker template, or perhaps the Docker template already has one added? Here's an unraid forum for tvheadend which has some code box/snips for --device; might give you pointers on how it gets done (from a 'high-level' general idea stand point): https://forums.unraid.net/topic/44872-support-binhex-tvheadend/ Not the silver-bullet, I'm guessing, you were looking for but some pointers to the direction you were looking for.
  3. I have about the same perspective, although I don't use unassigned drive for this (good idea though). Now that multiple-cache pools is a thing, I could see myself setting up a modest spinner drive as a cache drive for my BT share. Using an SSD as a cache drive for BT would be a hard-pass for me.
  4. This looks like a fun way to break my system, time to make a few redundant backups of my flash-drive. Thanks for posting all of this.
  5. Jcloud replied to Zotarios's topic in Docker Containers
    Hey, thanks for reading and trying to help me out, I appreciate the example. I've since resolved my issue by changing the Docker containers I use, streamlined things for my given task-set. I wasn't sure how helpful it would be, but thought maybe it held some insight for you - described symptoms seemed the same/similar to me. But that's all I presently got. GL Have a good one everyone.
  6. [BACKGROUND:] I would call this an edge-case, and just annoyance level of a bug - however I found this to be very annoying when caught in it. The Unraid webui, TOWER/Docker/, can be thrown into a refresh-loop - causing a number of page functions to stop working, or greyed-out, while the UI waits for the loop/task to stop. This was found trying to setup a VPN-client container and pointing a Torrent client container to the VPN container. [ISSUE:] When a Docker container fails to be edited/created (the container becomes orphaned) - expected behavior. If a container is linked to another container, such as using 'extra parameter' "--net=container:nordvpn" that container becomes dependent on the linked container - expected behavior. If the required container is edited/updated the other container also updates - expected behavior. If the required-container is edited incorrectly and fails creation/update the container becomes orphaned; Docker/webui notices the dependency-container has changed and attempts to update other container. However the second container fails to update, because the dependency-container has been orphaned - The Unraid Webui gets stuck in a loop trying to rebuild the container. Only way I found to stop this loop is to try and remove the second container; afterwards hit refresh button on web browser; and then remake both containers. On two occasions I was unable to remove the second container, and had to go into Settings and stop/start Docker completely. [STEPS TO REPRODUCE ISSUE:] 0* From APP store-plugin grab: nordvpn transmission 1* Per instructions from nordvpn - Overview: https://www.youtube.com/watch?v=znSu_FuKFW0 * Edit Transmission container settings: * Disabled network * 'Extra Parameters:' == '--net=container:nordvpn' * APPLY (webui) 2* Edit Nordvpn container * Make a change and save which will cause an error in updating/rebuilding the container and cause the container image to orphan (I did this as I was trying things to troubleshoot and get VPN-bittorrent to actually work). Example to cause container update failure: 'Extra Parameters:' == '--device /dev/net/tun --cap-add=NET_ADMIN,SYS_ADMIN' * APPLY (webui) The update to Nordvpn should have failed; taking user back to TOWER/Docker where the system attempts to rebuild Transmission and is stuck in a loop. This loop continues until the user removes the Transmission container, and hits the refresh button in web browser. --EOF I hope I outlined the issue enough to be useful, if there's something which needs better explanation let me know. Please move this post if it's in the wrong thread. Have a good one everyone! hydra-diagnostics-20210603-1246.zip
  7. Jcloud replied to Zotarios's topic in Docker Containers
    It appears that you aren't the only one: https://github.com/bubuntux/nordvpn/issues/75 Question of my own, what's the syntax format for the "Location" variable? I tried to use: "us8297.nordvpn.com" which resulted in, "[Warning] could not determine server tag" and "[Error] picking servers: no servers found" in the log window. If I leave the "Location" variable empty (let the docker/app auto-detect the server) the log stops at "Connecting..." 2021-06-03T10:01:46-05:00] Firewall is up, everything has to go through the vpn [2021-06-03T10:01:46-05:00] Enabling connection to secure interfaces [2021-06-03T10:01:46-05:00] Enabling connection to nordvpn group [2021-06-03T10:01:46-05:00] Enabling connection to docker network [2021-06-03T10:01:46-05:00] Enabling connection to network 192.168.100.0/24 [2021-06-03T10:01:46-05:00] Restarting the service [2021-06-03T10:01:46-05:00] Waiting for the service to start [2021-06-03T10:01:47-05:00] Logging in [2021-06-03T10:01:53-05:00] Setting up NordVPN Version 3.9.5 CyberSec is already set to 'disabled'. DNS is set to '1.0.0.1, 1.1.1.1, 8.8.8.8' successfully. Technology is already set to 'OpenVPN'. Subnet 172.17.0.0/16 is whitelisted successfully. Subnet 192.168.100.0/24 is whitelisted successfully. Port 9091 (UDP|TCP) is whitelisted successfully. Port 54321 (UDP|TCP) is whitelisted successfully. [2021-06-03T10:01:53-05:00] Connecting... Just edited the container, adding environment variable DEBUG=on; no new information. [2021-06-03T10:10:09-05:00] Firewall is up, everything has to go through the vpn [2021-06-03T10:10:09-05:00] Enabling connection to secure interfaces [2021-06-03T10:10:09-05:00] Enabling connection to nordvpn group [2021-06-03T10:10:09-05:00] Enabling connection to docker network [2021-06-03T10:10:09-05:00] Enabling connection to network 192.168.100.0/24 [2021-06-03T10:10:09-05:00] Restarting the service [2021-06-03T10:10:09-05:00] Waiting for the service to start [2021-06-03T10:10:10-05:00] Logging in [2021-06-03T10:10:21-05:00] Setting up NordVPN Version 3.9.5 CyberSec is already set to 'disabled'. DNS is set to '1.0.0.1, 1.1.1.1, 8.8.8.8' successfully. Technology is already set to 'OpenVPN'. Subnet 172.17.0.0/16 is whitelisted successfully. Subnet 192.168.100.0/24 is whitelisted successfully. Port 9091 (UDP|TCP) is whitelisted successfully. Port 54321 (UDP|TCP) is whitelisted successfully. Protocol: UDP Firewall: enabled Kill Switch: disabled CyberSec: disabled Obfuscate: disabled Notify: disabled Auto-connect: disabled DNS: 1.0.0.1, 1.1.1.1, 8.8.8.8 Whitelisted ports: 9091 (UDP|TCP) 54321 (UDP|TCP) Whitelisted subnets: 172.17.0.0/16 192.168.100.0/24 [2021-06-03T10:10:21-05:00] Connecting... [2021-06-03T10:10:21-05:00] Setting up NordVPN Version 3.9.5 CyberSec is already set to 'disabled'. DNS is set to '1.0.0.1, 1.1.1.1, 8.8.8.8' successfully. Technology is already set to 'OpenVPN'. Subnet 172.17.0.0/16 is whitelisted successfully. Subnet 192.168.100.0/24 is whitelisted successfully. Port 9091 (UDP|TCP) is whitelisted successfully. Port 54321 (UDP|TCP) is whitelisted successfully. Protocol: UDP Firewall: enabled Kill Switch: disabled CyberSec: disabled Obfuscate: disabled Notify: disabled Auto-connect: disabled DNS: 1.0.0.1, 1.1.1.1, 8.8.8.8 Whitelisted ports: 9091 (UDP|TCP) 54321 (UDP|TCP) Whitelisted subnets: 172.17.0.0/16 192.168.100.0/24 [2021-06-03T10:10:21-05:00] Connecting... If I open the console for the Nordvpn container, and type the CLI: "curl ifconfig.io" the reported IP address is NOT my WAN IP, but appears to be a NORD server/node: 207.38.90.204. However, when I open my Transmission docker container (modified per spaceinvader video - 97%-certain it's correctly modified). The Webui is unable to reach Transmission backend (server not found). Per the Docker documentation I added an environmental-variable 'PORTS'='9091,54321' -- this change allowed me to access the Transmission-webgui. Anyone have ideas on how to resolve or further troubleshoot? EDITED: I think figured out my issue; NordVPN everything was working normally, but Transmission only had the tunnel and not an IP address, so when I tried to access it from web-browser the errors were from cached info from previous changes in settings. I couldn't figure out how to resolve the issue, so I changed programs, moved to binhex-delugevpn. Have a good one everyone.
  8. Jcloud replied to unraid888's topic in VM Engine (KVM)
    Full disclaimer, I'm not an expert, however I did notice you're using q35-5.0 machine type in your VM's-XML; my w10-vm uses pc-i440fx and it was just last week I upgraded from 6.8.3 to 6.9.1 without issue. Perhaps this is part of your boot issue? Why it would have been working while Unraid was 6.8.3 versus 6.9.x I do not know, but (on my system) starting a new "Windows 10" template the machine type defaults to the i440fx type. Are there specifics why you're using q35 machine type (I'm just curious)? ... Never mind, I just made a VM with q35 machine type and it booted up no issue, so ignore my ignorance about machine types - but perhaps that's playing into things? (again IDK just grasping at "plausables" ideas to test and troubleshoot) Last line of your log screen shot showed it couldn't reset 0000:lf.5 which I think is the controller you stubbed out? (last screen shot, still learning new 6.9.x features - haven't played enough) Perhaps trying to uncheck that controller, reboot and give the VM another try? Probably not that useful info, but if it was me I would investigate/troubleshoot that device next. GL
  9. I think that's a great summation. I love Unraid but if I needed a straight up NAS solution I'd take a hard look at FreeNAS (and Synology). I had a DM chat with a FreeNAS user on Imgur; I was impressed with a few FreeNAS features, but the BSD-hypervisor was badly lacking in comparison to Unraid's/Linux-KVM (which makes Unraid the winner for my use-cases). Okay, I'm done beating the dead horse. Have a good one, everyone.
  10. Just saw this (paid attention to forums) I'll take a look at it in a few, do some reading, probably make the tweeks. Thanks for pushing on my radar. Sent from my SAMSUNG-SGH-I537 using Tapatalk
  11. The docker container, or something else? Assuming you're talking about the Docker container; open the Unraid webgui, click on Docker menu, on the line for the container click "force update."
  12. It's the first line in the dashboard, "ID" - I believe that is it.
  13. Ah. 1gb, nice, way better then anything available to me in my area. I used to run into the problem you have, with my torrent client, prioritizing network at my router fixed the issue (for me). I might look into it, time permitting.
  14. Yup. It is the underlying idea of what what you want, as a proof of concept example. Perhaps, why not submit the idea to them directly? https://ideas.storj.io/ This software is only an ALPHA stages after all.
  15. Best I could think of would be to setup some kind of QoS, and/or traffic shaper, on your router if it's supported feature of the device. From the Docker itself, I'm unaware of any such bandwidth limiter.