nblain1

@TheInfamousWaffles I am not running a bonded connection, but I do run a bridge, but I understand that you can bridge a bonded connection to allow VMs and dockers to communicate. I would suggest enabling bridging in your network settings and then running the Pi-Hole Docker in Network Type: br0 and setting a custom (unused of course) IP address and it's default port of 80. This is my setup and I have no issues running Unraid's web UI on port 80 (server ip ending in .254) and Pi-Hole's UI port on 80 (Pi-Hole's ip ending in .253).

@TheInfamousWaffles with a quick look over I see that you are putting your DNS for the docker as itself... I am not saying mine is configured correctly, but I have my dns severs set up as traditional servers (i.e. 1.1.1.1 and 1.0.0.1) Here is a screenshot of my config. Unraid IP is .254 and Pihole is .253 for clarification of screenshot. Also, I setup with the help of this video:

So, I still experience this problem on every release from 6.8.0-rc3 to rc6. Not sure where to go from here... I feel like I've tried everything in my book of tricks. My only option I see now is running Pihole in a VM which will require more resources. Pihole docker works perfectly as long as any VMs are not using the br0 bridge. If I set them to virtb0, then Pihole will work with VMs running, but I lose the ability to remote connect to the VMs as they are on a different IP address range. If anyone has any ideas, I am more than willing to try them out! Thanks in advance.

@spants - I don't thing so... the br0 interface is up and running with PiHole working, but as soon as I fire up any VM internet cuts out because PiHole goes unresponsive (loses access to br0 somehow). I will paste a portion of Unraid's log below showing what happens when a VM is enabled then disabled. PiHole and VM logs show nothing out of the norm. Oct 28 11:38:48 Tower avahi-daemon[9683]: Joining mDNS multicast group on interface vnet0.IPv6 with address f----identifier removed----c. Oct 28 11:38:48 Tower avahi-daemon[9683]: New relevant interface vnet0.IPv6 for mDNS. Oct 28 11:38:48 Tower avahi-daemon[9683]: Registering new address record for f----identifier removed----c on vnet0.*. Oct 28 11:38:58 Tower avahi-daemon[9683]: Interface vnet0.IPv6 no longer relevant for mDNS. Oct 28 11:38:58 Tower avahi-daemon[9683]: Leaving mDNS multicast group on interface vnet0.IPv6 with address f----identifier removed----c. Oct 28 11:38:58 Tower kernel: br0: port 2(vnet0) entered disabled state Oct 28 11:38:58 Tower kernel: device vnet0 left promiscuous mode Oct 28 11:38:58 Tower kernel: br0: port 2(vnet0) entered disabled state Oct 28 11:38:58 Tower avahi-daemon[9683]: Withdrawing address record for f----identifier removed----c on vnet0. 1st line from VM started. 5th line from VM stopped.

On Unraid 6.8.0 rc3 I've noticed if I enable my VMs that use br0 (Pihole uses same bridge), Pihole is inaccessable. The webui for Pihole comes back as soon as I shutdown my VMs. EDIT: Just updated to 6.8.0 rc4 and now Pihole and my VMs are running together and playing nicely. Not sure what the problem was on rc3... EDIT 2: Spoke too soon... seems to still be happening..

Thanks fryfrog! I think this may be an issue for the Unifi forums, but I guess its worth checking here.... I nuked my installation because I cannot connect my docker to the Unifi Cloud so I can remotely view my cameras. I go through the process, it finds my NVR, and stays on the connected screen until it times out with an error reading "cannot connect to NVR" but if i go back to the UI for the docker under settings it shows my NVR is connected to the cloud anyways. I try to connect to my cameras using the iOS app and although my NVR shows up I cannot connect to it. Not sure if this is a common problem already solved by someone on this forum, or if I will have to dig deep on this one. I have tried with a completely fresh NVR docker and I still get the same behavior. I am using Chrome with the Device Discory Tool from Ubiquiti installed.

I made a backup within Unifi-Video and nuked my docker installation (deleted the appdata folder as well). Now after a fresh docker pull from CA and setting the is_default=true setting within system.properties, the docker log shows "(unifi-video) checking for system.properties and truststore files... done." and the docker will not load the web ui for Unifi-Video. If I remove the system.properties file the webui will appear but login is not possible, obviously. I am not sure what else I can try from my end to get this docker back up and running. Steps Taken: 1. Delete docker and image 2. Remove dangling images from docker using user scripts 3. Remove docker template from previously installed dockers within CA 4. Create appdata folder with a system.properties file with is_default = true 5. Install docker making sure folder mappings are correct I have also tried skipping step 4 and starting then stopping the new docker install and then creating the system.properties file. The docker seems to only use about 8mb of ram and a very small amount of CPU while its in the hanging state with the system.properties file present with is_default=true.

I am having a problem with pihole running alongside vm manager. I never used vm's but I recently set a Win 10 vm up. Shortly after running the vm i noticed my pihole docker container was stopped. I did some testing and it seems that port 53 is taken when running vm manager even if no vm's are running. Pihole is running bridge with ports 53 and 80. Unraid gui moved from 80. docker using 172.17.0.0/16 vm manager 192.168.122.0/24 I feel like I am missing something obvious. I can post configs or diag if this isn't enough. EDIT (Solved): It was a stupid, simple mistake. For others who may have overlooked this, during setup of my VM in Network Settings for Unraid I moved to 'bridged' mode. Because of this when launching or installing Pi-Hole I needed to set its connection/interface from eth0 to br0. That's it..... smh.

Pducharme, I have installed the Unifi Video container and set it up. I am trying to view a live feed from within Unifi Video but I am having port issues. I have forwarded the ports used by the container to my Unraid IP address, but I still have no luck. Also, within the Unifi Video container it reports the UVC's IP address to be 172.17.0.10. Which IP address should I forward these ports to? I have tried both and nothing seems to work. I can view the feed if I log into the camera directly using its IP address. Solved: I ended up having to switch the container to host instead of bridge. Then I had to unmanage the camera and restart the container. Once restarted I logged back in and adopted the camera again. This allowed me to view the camera's feed from within the Unifi Video container. Hope this helps anyone with similar issues. I also had all ports used by the container (7443,7445,7446,7447,7080,6666,22) forwarded to my Unraid's IP address.

I also can't get the logs to work with rcloneCopy.sh. Code: LOGFILE=/boot/rclone/logs/rclone-$(date "+%Y%m%d").log echo rclone log $(date) $'\r'$'\r' >> $LOGFILE 2>&1 echo "Starting rclone copy" $'\r'>> $LOGFILE 2>&1 rclone copy /mnt/user/Pictures remote:Backup_Pictures >> $LOGFILE 2>&1 Error: : Invalid argumentts/rcloneCopy.sh: line 2: /boot/rclone/logs/rclone-20160607.log : Invalid argumentts/rcloneCopy.sh: line 3: /boot/rclone/logs/rclone-20160607.log : Invalid argumentts/rcloneCopy.sh: line 4: /boot/rclone/logs/rclone-20160607.log I can get these commands to work manually copying and pasting them in a telnet session. I tried adding delays, but that didn't help. Not sure why this code isn't working from a script.

Sorry for my ignorance, but what is the default password for unifi-video? root/ubnt? Edit: To elaborate I have done a fresh install of the docker and deleted the appdata folders. On startup I am greeted with a unifi-video login screen and no wizard. In the unifi-video appdata folder there is no system.properties files even being created anymore.

The docker is installed to and running from my cache drive (specifically /mnt/cache/appdata and NOT /mnt/user/appdata). Is this the correct mapping scheme? Also when you edited system.properties how did you do it? Did you ssh to unRaid directly and use nano or just a word editor from a networked machine? Also, am I correct when I login as root to edit the file using SSH and nano?

I have installed Unifi-Video, but I cannot get it to start for the life of me. I let it create the files and folders within my appdata folder. I have stopped the program and edited system.properties to include "is_default=true" (without quotes) on the first line. I have also repaired permissions after this action and restarted the docker. Once restarted I see nothing in the docker log. What I am doing wrong? I have used nano via putty to edit, as well as, word pad through file explorer. I have repaired permissions before starting, as well as, delete all the files and start fresh multiple times. I have yet to get the docker to actually load. error.txt

Would HDhomerun allow me to pause on a device that does not have storage? I would like Unraid to handle the storage with recording and pausing.

I have been searching for information, but a lot of it seems old information our just over my head. I am trying to find a TV Tuner for Unraid that will allow me to record a show or two and watch a different channel at the same time over my network. I am in the US and right now we are using an OTA Antenna for TV, but I would also like a tuner that would also do cable down the road if I had a cable card. I would be using Kodi for watching the TV signals over my home network from various rooms running HTPC's and Raspberry Pi 2's. So in short I need a tuner for: 1. Antenna Signal and Cable compatible in the US 2. Supported by Unraid (and Kodi?) 3. Can be used to stream channels over network to other locations in home using Kodi for playback I am running Unraid 6 with a Cache SSD

SOLD! Thanks Dease!

I am interested, but my budget isn't much over $350. If you would like to work something out let me know. Thanks!