Celsian

Thanks for your help!

Looks like the dreaded SSL issue is back for pip, see attached. I didn't see any answers previously in this thread other than needing to wait for an update. Is that still the case? Edit: Turns out the Repo was updated 11 hours ago with a new version of Python3 (3.9.17) that does not have SSL by default. The old package version 3.9.16 does. Hopefully this will get fixed soon. This support thread in Trash guides discord helped me figure out what was going on and install an older version of Python 3 that worked. Here's the two commands to run in the Unraid console to install the older version. If you already installed Python3 through the NerdTools pack, remove it. Do install python-pip & python-setuptools via NerdTools. wget -O /boot/extra/python3-3.9.16-x86_64-1_nerdtools.txz https://github.com/UnRAIDES/unRAID-NerdTools/raw/d01098b77b82c1d12a8491d988da2db7f66d9f40/packages/6.11/python3-3.9.16-x86_64-1.txz installpkg /boot/extra/python3-3.9.16-x86_64-1_nerdtools.txz --reinstall

Turns out the problem was actually with my network settings, when I restarted my unRAID server, the network connections stopped working again for both VM's. To resolve it I discovered that under network settings I had to enable bonding for eth0. I enabled bonding for the NIC, set the mode to backup and only included eth0 in the bond. After starting the VM's again, their network connections started working and the connections continued working after an unRAID restart.

I fixed this issue by switching the VM Network Model from virtio-net to virtio. I have no idea why that fixed it.

I resolved this issue by changing my network model for my VM's from 'virtio-net' to 'virtio' Does anyone know why virtio-net does not appear to work anymore?

I have two VM's, Debian and Win10. Neither can ping any ip address other than the unraid ip. Pinging the router or any external address fails. Here is my network config:

Thank you for the response, it seems to be better today after I restarted the container. Maybe something funky was going on. I'll keep an eye on it and ask there if it comes back.

I only recently got back into V Rising and decided to spin up my own server via a docker container. When playing, I get occasional micro stutters. The stutters are noticeably worse after about 24 hours of up time. I'm the only one on this server at the moment. This doesn't happen when I'm playing on a friends hosted server. Is there some sort of special resources setup I should be doing for this docker? I'm using a Ryzen 3900x with 64gb of 3200mhz memory. My CPU usage doesn't appear to go over 15% when I'm logged into the server. It has a Raid 1 cache drive setup with two 970 Evo Plus drives, which house my docker appdata folder. These are 85% empty. I do have several other docker containers running on the same machine, but none of them are game servers and appear to use very few resources.

If you're using Apache2, add this to your reverse proxy virtual host: RewriteEngine On RewriteCond %{HTTP:Connection} Upgrade [NC] RewriteCond %{HTTP:Upgrade} websocket [NC] RewriteRule /(.*) ws://<docker ip address>:<port>/$1 [P,L] Replace <docker ip address> and <port> with your OpenBooks ip address and webui port. Edit: You need the rewrite mod for this to work: sudo a2enmod rewrite

Just wanted to drop by and thank the dev. I had a power failure 10 hours into a 20tb preclear. Thanks to this plugin I was able to pause the preclear and let the unRAID server shutdown when my UPS batteries hit the low percentage mark. Upon power restoration I booted up and was able to resume the preclear. Thanks for saving me 10 hours of wasted time.

Same for 2 containers.

dg180, I found some information in another thread about this being an unRaid implementation issue. It's supposed to be fixed in the next version. In the mean time you can use the community application linked in this thread to fix things, it's called 'docker patch' Apparently the community app is set to not install on unRaid after version 6.11.5, so you shouldn't need to remove it later, it will remove itself.

Is anyone having trouble keeping jellyseerr up to date? I constantly version not available with the broken link icon next to it. See the attached image. Jellyseer works fine and I'm able to force update it. I only realized this was an issue when I found that I was several revisions behind despite automatically updating my docker containers nightly.

Small update. After fixing my Passthrough issue (earlier in this thread) the VM has been working flawlessly since. Upgrading to 6.11 worked fine. Passthrough continues to work. Edit: 11/28/22 Passthrough still working as of 6.11.5 Another note, I recently helped my brother with his GTX 770. The steps I took above did not work for that card, we were still getting Error code 43 in device manger, however a change to the VM's XML from this post fixed it:

I likely could have sysprepped it and moved it over that way, but I didn't think to do that until after I had already started setting up the new one. I've installed windows hundreds of times and this VM is just an HTPC anyway, so there's not a lot of setup necessary. Obviously that's not the case for everyone else, sysprep is a great alternative.