BBLV

That worked! Not sure why I thought the steamcmd was the right folder... Thanks for the help.

DId you get this figured out? I haven't launched Palworld in over a year (worked great before) and I'm getting the same error you are when trying to connect to the game server (server version is an older incompatible game version). I deleted the steamcmd appdata folder, restarted the Palworld docker, and still same issue when trying to join the server. My docker log says it's running Palworld v0.7.1.86065 and the Palworld game says it's running v0.7.2.87654 any way to force the docker to pull down the latest matching version from Steam?

Redid the whole process with new VPN credentials and new OpenVPN config file and we're back up and running! Thanks for the help, yet again.

I haven't changed anything except updating the OS, so it's odd that it would randomly have that issue. I haven't checked into Tailscale yet, but would you recommend moving to it from OpenVPN? It may fix my issue?

Log attached. supervisord.log

Just pulled down that test version and same issue - WebUI cannot be reached.

Same here. Been running great for years, then I update to a new OS version and can't access the WebUI. Not sure where to go from here. Have you been able to figure this out?

Is there a new version of OpenVPN that is preferred, now that this is deprecated? Still working fine for me but curious.

This saved me after countless hours of searching for a fix and tinkering... My VM's stopped working out of nowhere and this was the solution to get them back up and running. I would get errors when trying to start my VM's and my log was 100% full (due to the VM errors spamming the syslog). I know this is a fix, but what is the underlying issue that is causing this? Something seems very broken for this to just happen randomly...

I swapped my Nvidia 2080 card back in and the mouse polling rate stutter/lag issue disappeared! I just took the AMD 6900XT card back to Microcenter, then bit the bullet and ordered a 3090 card. I'll report back here if the issue is isolated to the AMD card in MY system. Seriously weird issue.....

So I passed through my PCIE USB controller and am still getting the mouse lag/stuttering that scales with the mouse polling rate on my Logitech G502. Not sure what to tweak next, but this is starting to piss me off..

Thankfully I have the same Inatek PCIE USB 3 controller that SpaceInvader used in his pass-through YT video, so that's my next step in troubleshooting (just need to find the extra time in the day!). FWIW I'm currently passing the mouse and keyboard through individually by just checking the boxes in the VM Advanced View... Thanks again for the tip that got me moving in the right direction!

Tried this - no improvement for me, but thank you for the recommendation.

Surprisingly, reducing the mouse's polling (report) rate from 1000Hz to 125Hz made the game's fps actually playable (I'm using a Logitech G502 wireless gaming mouse). It still has a noticeable blip/stutter when I move the mouse to look around in-game, but at least we're narrowing down the issue. The weirdest part to me is that I had no issue with this with my prior VM setup with the Nvidia 2080.... I'm scouring the web trying to find a permanent fix for this to do away with as much latency as possible - stumbled onto something about replacing virtio drivers for PS2/USB devices, but more research and tinkering to do.

Interesting... I haven't yet passed through my USB 3 PCI card, but maybe I should try that along with tweaking the mouse settings to see if that fixes the issue.

I just swapped out my GPU (2080 upgraded to a 6900XT) and I'm getting severe stuttering/lagging in games and microstuttering in Win10 (i.e. slight jumpiness moving windows around, etc). I believe I've properly pinned my 2920X TR2 CPU and adjusted my XML for the GPU/HDMI audio properly, but could use some expert feedback. I've scoured the forum for answers, but nothing has seemed to correct the stuttering. I'm a noob with VM's and XML editing - I'd greatly appreciate if someone could take a quick peek and let me know if they see anything obvious that could be causing a conflict. Here's my full XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>b9a3b51e-52b7-ad1e-2fd5-0aca043e6897</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>20971520</memory> <currentMemory unit='KiB'>20971520</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='18'/> <vcpupin vcpu='2' cpuset='7'/> <vcpupin vcpu='3' cpuset='19'/> <vcpupin vcpu='4' cpuset='8'/> <vcpupin vcpu='5' cpuset='20'/> <vcpupin vcpu='6' cpuset='9'/> <vcpupin vcpu='7' cpuset='21'/> <vcpupin vcpu='8' cpuset='10'/> <vcpupin vcpu='9' cpuset='22'/> <vcpupin vcpu='10' cpuset='11'/> <vcpupin vcpu='11' cpuset='23'/> <emulatorpin cpuset='0,12'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/b9a3b51e-52b7-ad1e-2fd5-0aca043e6897_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='6' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <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='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.215.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/nvme-Samsung_SSD_970_EVO_1TB_S467NX0KB29066F'/> <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='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </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> <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='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <interface type='bridge'> <mac address='52:54:00:91:2b:1a'/> <source bridge='br0'/> <model type='virtio-net'/> <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='3'/> </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='0x44' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/Sapphire.Nitro.SE.6900XT.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x44' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc539'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x1b8f'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> </domain>

I'm getting severe stuttering in games making them unplayable. I believe it may be caused by my XML setup of my GPU/audio bindings. For some reason the GPU and onboard audio are showing up on different buses and I can't figure out how to get them to group into the same slot (and assumably use multifunction on the GPU). Any idea on how to rectify that and hopefully cure my stuttering? Here's a snippet from my XML: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x44' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/Sapphire.Nitro.SE.6900XT.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x44' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev>

I pulled the attached vbios via GPU-Z from my new AMD Sapphire Nitro+ SE 16GB RX 6900 XT GPU. Please add to the repository. RX 6900XT - Sapphire Nitro+ SE - 16G.rom

Ok I'm a complete fool. I actually have three different LAN ports and thought I had the right one. Tried the third that I couldn't see from my angle behind the rack and USB devices and sure enough, back to normal... Thanks for taking the time to help me out here, yet again!

I believe I have a networking issue caused by some BIOS tweaks. I updated my BIOS at the same time that I was tweaking settings to try to get Unraid to boot after the GPU swap that may have led to some PCI glitch? I'm going to delete my network.cfg file to reset my network settings and see if that will at least allow me to access the GUI.

Here's the full zip bserver-diagnostics-20220112-0015.zip

Oddly (and I'm not sure if this is the issue) my eth0 and eth1 show different MACs in different config files. In the syslog eth0 shows the MAC address as b4:2e:99:32:d5:73 but in network-rules.cfg eth0 shows as b4:2e:99:32:d5:77... And conversely, eth1 shows as b4:2e:99:32:d5:75 in syslog but shows as b4:2e:99:32:d5:73 in network-rules.cfg? My BIOS shows that my active "connected" NIC is MAC address b4:2e:99:32:d5:73 at PCI address 03:00:00 which corresponds to eth0 in the syslog. I'm very confused LOL network-rules.cfg

And my network config file. network.cfg

Here is my diagnostics file. syslog.txt

I believe I've narrowed it down to a NIC issue. I can't ping out or in, just get the error "destination host unreachable"... Could this be a BIOS setting issue? Anyone have any tips to get the Network interface working with Unraid?