bellyup

Are you sure you passed your device into the docker container?

I would GREATLY appreciate some help with my routing table. My main network is 192.168.1.0/24 and my VPN network is 192.168.2.0/24. When I'm connected by VPN I can't access my unraid server. Would it be a problem with my routing table entries? Can I clean up some of those routes I have? for example the shim-br0? I really don't know what I need to keep and what I need to add and what the difference in the gateway effects it.

I post to quickly without thinking... I had IPv6 DNS entered in my pihole container. I'm going test. Deleting this post.

Is this normal? Mar 28 14:37:26 R720 avahi-daemon[10445]: Joining mDNS multicast group on interface vethbd239d6.IPv6 with address fe80::d46f:a5ff:fe4d:a4cd. Mar 28 14:37:26 R720 avahi-daemon[10445]: New relevant interface vethbd239d6.IPv6 for mDNS. Mar 28 14:37:26 R720 avahi-daemon[10445]: Registering new address record for fe80::d46f:a5ff:fe4d:a4cd on vethbd239d6.*. Mar 28 14:37:30 R720 kernel: eth0: renamed from vethd648de3 Mar 28 14:37:30 R720 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb54df6f: link becomes ready I don't have it in my network settings as being on. "IPv4 Only"??

Your awesome. Thank you very much.

I was using the network daughter board in the past but I only have one port active now. The other card and onboard are disabled in the bios. I get the Error Found from "Fix common plugin app": eth4 and eth8 both have IP addresses on the 169.254.0.0 network. This is rarely a valid configuration I've tried to delete all of these entries by clicking the trash can but they don't delete. Everything works but is there a simple way to fix this? IPv4 default br4 via link 210 IPv4 default br8 via link 211 IPv4 169.254.0.0/16 br4 210 IPv4 169.254.0.0/16 br8 211 Thanks for any help you can offer.

Thats exactly what I'm doing. You're brilliant! I was using the web client (multiple times on one pc) to run multiple streams for testing transcoding and I was forcing the quality change. I wanted to test the not only that it was transcoding but that it was running more than 2 concurrent sessions. I just got to work so I can't test until much later tonight but thank you so much. EDIT: I would like to confirm that was my problem and my transcoding was been fine the whole time. The way I was testing it was wrong. LOL? More sad than funny but thank you!

That PSU calculator is pretty cool! Thank you so much for your response and help. With my basic items in the calculator it does recommend I use ~600w so 750w should be fine. I've already ordered the 1100w so I will install them anyway and see... in march. Shipping to canada is never great.

I'm feeling a little silly because I think I just realized what my issue is with this patch and my hardware setup. I believe the issue I have is not with the patch but with my hardware setup. Please review and comment if anyone can? I have a DELL R720 with a gtx 1650 turbo and two 750w power supplies. My card is recognized and it starts to transcode but quickly fails and kills the processes. I didn't even clue in that I only had 750w power supplies or that it wouldn't be enough until I was physically changing my setup for something else. Does it seem plausible that my ps is too weak and when the GPU starts to draw anything beyond idle it fails? I've ordered 2 1100w power supplies (wont arrive until mid march!) but I like to know if anyone can comment... even if its "you idiot of course you need a larger ps when you add a gpu!"

I’m sorry you are correct. I’m not running unraid in a vm; however, the issue of it starting to transcode then crashing is what happens to me also. I was just going to wait for the full 6.9 release before doing anything else but I’m happy to help if you want any further testing.

I had the same issue with my gtx 1650 turbo. I was unable to fix it.

I have a very similar issue with one of my drives. Do you make any progress or what are you doing keeping or replacing? Are you on stable or next? I'm running RC3.

Im very sorry. Thank you.

I went right from 6.8.3 to rc2 so I have to go back to that then forward to beta35. Thank you so much for commenting and helping I really appreciate it, you saved me so much time of messing around and attempting to trouble shoot.

Thank you very much, I will try right now.