ritty

Thanks @JorgeB, appreciate the response. Will keep an eye on docker but everything seems okay so far. Appreciate it!

I was in my system logs (which I never check) and noticed some weird logs as shown below. Can anybody explain what these mean and if i should be modifying something in my configuration? I appreciate your help in advance as I am not smart but I do love Unraid. Thank you. Dec 31 08:20:39 JamFlix kernel: eth0: renamed from vethed5eb14 Dec 31 08:20:39 JamFlix kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth583b29d: link becomes ready Dec 31 08:20:39 JamFlix kernel: br-e494ce73ff26: port 29(veth583b29d) entered blocking state Dec 31 08:20:39 JamFlix kernel: br-e494ce73ff26: port 29(veth583b29d) entered forwarding state Dec 31 08:30:01 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered blocking state Dec 31 08:30:01 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered disabled state Dec 31 08:30:01 JamFlix kernel: device veth9cdb3e1 entered promiscuous mode Dec 31 08:30:03 JamFlix kernel: eth0: renamed from veth24f5098 Dec 31 08:30:03 JamFlix kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9cdb3e1: link becomes ready Dec 31 08:30:03 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered blocking state Dec 31 08:30:03 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered forwarding state Dec 31 08:30:04 JamFlix kernel: veth24f5098: renamed from eth0 Dec 31 08:30:04 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered disabled state Dec 31 08:30:04 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered disabled state Dec 31 08:30:04 JamFlix kernel: device veth9cdb3e1 left promiscuous mode Dec 31 08:30:04 JamFlix kernel: br-e494ce73ff26: port 30(veth9cdb3e1) entered disabled state Dec 31 08:42:20 JamFlix kernel: br-e494ce73ff26: port 19(vethf3c35f7) entered disabled state Dec 31 08:42:20 JamFlix kernel: vethaf8c910: renamed from eth0 Dec 31 08:42:20 JamFlix kernel: br-e494ce73ff26: port 19(vethf3c35f7) entered disabled state Dec 31 08:42:20 JamFlix kernel: device vethf3c35f7 left promiscuous mode Dec 31 08:42:20 JamFlix kernel: br-e494ce73ff26: port 19(vethf3c35f7) entered disabled state Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered blocking state Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered disabled state Dec 31 08:42:25 JamFlix kernel: device vethe0efc8f entered promiscuous mode Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered blocking state Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered forwarding state Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered disabled state Dec 31 08:42:25 JamFlix kernel: eth0: renamed from vethe9ade76 Dec 31 08:42:25 JamFlix kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe0efc8f: link becomes ready Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered blocking state Dec 31 08:42:25 JamFlix kernel: br-e494ce73ff26: port 19(vethe0efc8f) entered forwarding state

Thank you so much @binhex. That post is much appreciated! I am going to make the new network that you defined Your work is so appreciated! Cheers

It seems that the clients on the same subnet cannot talk to rtorrent AND the webUI cannot be accessed from a client on the same subnet. However, when I go onto my main LAN (10.0.0.0/24) with my macbook, I can connect to the webUI where rtorrent is on 10.0.20.0/24 subnet.... In the LAN_NETWORK field, I put 10.0.20.0/24 so I am so confused. How is it possible that clients on the same subnet can't even connect but on the main LAN, they can. I am starting to think this issue has to do with my Unifi Router. I checked my firewall settings and everything seems fine. So strange...

Can't access web UI means that when I try to open the container via the unraid GUI, the web page is stuck loading forever and never actually loads. In fact, the login popup doesnt even show up. Thanks for your tip, ill check into that.

Thank you for the reply. Very strange: RPC enabled. RPC username and password correct. Pinging from another container works. Can't access the web UI even though the logs show it's loaded....Sooo strange. I think I will just resort to bridge mode for these containers. Appreciate the help.

Hey guys, wondering if anybody has any ideas to help on this one? Thanks

I have tried everything so i want to resort here for a question that hopefully somebody can answer (thanks in advance for the kind soul haha). I setup a subnet for my unraid server. It is 10.0.20.0/24 for the unraid network. My main LAN is 10.0.0.0/24. I have rtorrentvpn running on the unraid network and I fixed the IP to 10.0.20.20. I put the variable LAN_Network = 10.0.20.0/24. What am I doing wrong? I can go to the 10.0.20.20 address in chrome and put in my username + password. It resolves fine! However, when I use sonarr, radarr and all of the other ARR apps, I cannot connect to rtorrent. I have tried putting the name of the container for the host. I have also tried putting the IP itself i.e. 10.0.20.20. The port number is 9080 so I know thats not the issue. I am out of ideas as i have tried a lot of different things. One thing i should mention is that when my unraid server was on my main lan (10.0.0.0/24), I didnt have any issues. I set the IP address fixed for rtorrentVPN to 10.0.0.20 and everything worked perfectly fine. It seems now that it is on a subet of 10.0.20.0/24, the ARR apps cannot communicate with rtorrentvpn anymore.....All of the ARR apps are on the same subnet and they all communicate with each other no problem. Only rtorrentvpn is having issues... Any ideas are appreciated.

A quick solution for hardware encoding with nvidia GPUs. Use this docker then replace the repository with "zocker160/handbrake-nvenc"...obviously make sure to set your nvidia gpu up in the template (similar to plex or other apps). Works like a charm - went from 30 mins down to 5 mins per movie Boooo ya

You are a guru and a wizard all in one. You are very very intelligent @ghost82 thank you for all of your great advice!!! Unreal Much appreciated.

The VM doesnt work unless i keep the bus as 0x00 so I think it needs to remain that way @ghost82 but my XML is below. Hopefully there is a good explanation <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Macinabox BigSur</name> <uuid>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</uuid> <description>MacOS Big Sur</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="BigSur.png" os="osx"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='6'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='7'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='8'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='9'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/8ea67332-9908-4c8e-88da-98c9babcf1b6_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Macinabox BigSur/macos_disk.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:d9:66:31'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/Downloaded Header Removed/DellGT640.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> </hostdev> <memballoon model='none'/> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=xxxxxx'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain>

I should also mention - my VM is no longer laggy.... I never connect a monitor to it. Rather, I sign in remotely to use imessage etc. This GPU passthrough sped things up IMMENSELY!!! Totally worth it.

Thank you @cat2devnull - I finally got it working!!! It took multiple things to make it work. This is what worked for me: 1. Assign graphics card, bios, AND sound card (from gpu) in unraid template. Press save. 2. Run @SpaceInvaderOne script macinabox_helper - did not remove topology, kept as "custom" and set first install to "no. 3. Edited the XML and made these changes: a) Set multifunction='on' for gpu b) Changed sound function from 0x0 to 0x1 c) Changed graphics bus from 0x03 to 0x00 on gpu AND changed slot from 0x00 to 0x03 since the 00, 01, and 02 slots were taken already (THIS STEP WAS THE CRITICAL STEP THAT TOOK FOREVER FOR ME TO GET) d) Changed sound bus from 0x04 to 0x00 and changed slot from 0x00 to 0x03 -> this needs to match the graphics address. BOOOOOOMMM and then it worked. Hope this helps somebody else. Cheers,

Thanks @cat2devnull. The information is much appreciated and I am sure that will help others get it figured out! I tried each of those and still ran into issues. With that said, I am also not as technically skilled as many on here so I guess I just accepted defeat and decided to buy an old 2015 mac to have as a imessage server. It's quick and snappy and runs Big Sur with zero issues so I am happy I don't have to deal with that major lag I was getting with the MacOS VM. Appreciated the good info and I truly hope it helps many others on this board! Cheers,

I've tried everything that i can think of at this point. I changed the SMBIOS to iMac13,1 to ensure my GT 640 would match the SMBIOS...still didn't work. I really wish i could get this to work as my VM is sooo laggy....If anybody has any suggestions at all to reduce the lag then I am all ears.

I have tried endlessly to get my GPU passed through. I have a GT 640 and want to use it with my Big Sur VM created with macinabox. I followed all of the instructions perfectly in the @SpaceInvaderOne video and I also got imessage working by following the dortania guide. With all of that said, I tried passing through my gpu and then i get this error in the logs: 2021-08-24T02:53:13.110949Z qemu-system-x86_64: -device vfio-pci,host=0000:0c:00.0,id=hostdev0,bus=pci.3,addr=0x0: Failed to mmap 0000:0c:00.0 BAR 1. Performance may be slow I am running this VM headless but have a HDMI dummy plug. I highly HIGHLY recommend to save your XML before trying to do GPU passthrough. I know for me when i removed the GPU passthrough and went back to VNC, I could not get the Big Sur VM to start.... I re-pasted the original XML for the VM and boom it works fine. With that said, no matter what I try for GPU passthrough with my GT 640, it doesn't work. I know its not working because i have teamviewer installed and have my VM auto-login. If anybody has ANY suggestions, I am willing to try anything. I think OSX requires a GPU because my VM is super slow...All of the animations are so choppy and i feel like a GPU will fix this slow performance issue. Suggestions?

Let people know your problem... Pull the container using CA, and make sure you enter the mount name like "NAME:" In the host (aka Unraid) terminal run the provided command on page 1 of this post: docker exec -it Rclone-mount rclone --config="/config/.rclone.conf" config Follow the onscreen guide; most flow with other tutorials and the video referenced above. UNTIL - you get to the part about using "auto config" or "manual". Turns out it is WAY easier to just use "manual" as you'll get a one-time URL to allow access for rclone to your GDrive. After logging in and associating the auth request to your gmail account you'll get an auth key with a super easy copy button. Paste the auth/token key into the terminal window Continue as before, and complete the config setup CRITICAL - go to: cd /mnt/disks/ ls -la Make sure the rclone_volume is there, and then correct the permissions so the container can see the folder as noted previously in this thread chown 911:911 /mnt/disks/rclone_volume/ *assuming you're logged in as root, otherwise add "sudo" Restart the container, and verify you're not seeing any connection issues in the logs From the terminal cd /mnt/disks/rclone_volume ls -la Now you should see your files from GDrive

anybody have any recommendations for rtorrentvpn??

Has anybody got Uptime Kuma to work with rtorrentvpn?? It seems impossible to get it to work. I have ten other dockers working fine. I tried all the ports baked into rtorrentvpn container and then I also opened new ports to try and see if that works but it did not. Curious if anybody got binhex-rtorrentvpn to work with uptime kuma?

So happy. This container isn’t just read only. I mounted gdrive and can write sonarr and radarr etc to it with all the content I want. i was getting major issues with the rclone plug-in so I am so thankful you made this docker. I am a huge fan as I pulled my hair out trying to get the plug-in to work but it just randomly stopped working one day and I could never get it to work again. Please keep this container alive as it definitely is a great alternative to the plug-in.

Is this rclone docker a read only? Is it possible to remove the —read-only flag and then transfer data to gdrive with Krusader or another similar program?

I read through this forum before asking this question. Question: How can I get the "WebUI" button in the dockers tab for binhex-plex or binhex-plexpass? Background: I know this particular docker was meant to be in "host" mode but that doesn't work for my setup. I have all the dockers on a subnet together with each one having their own IP. As soon as I switch it away from host mode, the WebUI button when I left-click on the plex docker disappears. I read through this forum and another person had the same issue. Binhex said to add the ports needed by Plex and that will solve the issue. I tried that and the issue persists. I added other plex dockers to see if they encounter the same problem and they don't. With that said, I am a huge binhex fan and dont want to switch. Plus my library is already 100TB so switching now could be one massive task. I am hoping there is a solution that I haven't read in this forum or else an easy way to solve this problem. I understand its not like it's absolutely needed to have that webui button but plex is kinda difficult since it is the only docker i have where i can't just type in the IP and the port...it requires that web/index.html as well which gets lengthy and annoying. Any help is appreciated.

You are MY HERO!!! I’ve been having to stop my array a lot lately due to config upgrades and it was becoming cumbersome. Thank you so much. You are much appreciated. I’m sure many others will find this helpful as well

I’ve tried stopping dockers before shutting down three times and it still hangs. I don’t use VMs so I know that’s not an issue. I guess I’ll just keep shutting down using the current method. If anybody does create an unmounting script that confirms uploads are complete and then proceeds with unmounting, it would be greatly appreciated if you shared with the group I’m still very appreciative of this awesome plugin. it definitely makes my life a lot easier thank you

I am having similar issues as you. I cannot stop my array whatsoever because of rclone. I ssh'd into unraid then ran ps -ef | grep /mnt/user only to notice that rclone was still mounted... Has anybody created a safe user script to unmount drives for a safe array stop/unraid reboot? I would prefer not to run ps -ef | grep /mnt/user and then kill {pid} every time i stop the array....any help would be appreciated big time