• Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About Alexstrasza

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That's a pretty strange issue, that's not the error you should get if it's a SMBv1 problem from what I know, the error is normally much more specific. Have you tried posting a general thread in They'll be much better prepared to help you there, this is more of a support thread for Tailscale-specific issues. Unfortunately I think if your non-Tailscale file transfers don't work properly, they are unlikely to work within Tailscale, as the method is exactly the same.
  2. What exact error is it you are getting?
  3. Have you made sure Privileged is ON?
  4. Hi there, no, no more complete panics since then. I've had quite a lot of general instability issues, the X470D4U motherboard seems to be plagued with issues, in particular reliability varies hugely BIOS to BIOS, so if you're running that motherboard then I heavily recommend the P3.50 BIOS firmware and 2.20.00 BMC firmware, which have been the most stable I've seen. It's also worth noting that future UnRaid versions have also improved other issues a lot, so I heavily recommend checking you are on the latest version as well.
  5. There was a bug with older versions of QEMU where the host-passthrough CPU mode would not work. This is fixed in later versions of UnRaid. There's this really understated warning in the motherboard manual which has caught me out before and might be your problem too: The setting isn't called exactly the same thing as the manual says either (so that's helpful), but you need to manually switch the slots into 2x8 mode for either to work properly with two GPUs installed on a Ryzen 3000 series CPU.
  6. Correct on all three counts! However there is a bit more nuance to it. Whilst Wireguard can be used with a kernel implementation (which I believe is more efficient, so less CPU usage) it can also be implemented in software. Tailscale at the moment exclusively uses the software implementation to ease cross-platform compatibility, although there are plans in the future to link in with the kernel system on systems with support. This means it's technically not speaking with the system implementation at all at the moment. As for compatibility in general, as far as I'm aware any number o
  7. They can both run independently, so feel free to try it out!
  8. Good to hear! I'm glad I'm not going insane :). Unfortunately I still can't see the button because of another error: key [iManufacturer] doesn't exist Sounds like it's the same thing again but for this key 😅. I wonder what it's trying to read that lacks these values?
  9. Hi John, Am I going insane, or did there used to be a "Benchmark all" button or something to that extent? The only 'multiple benchmark' button I can find is under the controller info, and that seems to just check for a controller bottleneck. Also, when I look at the "USB Bus Tree" page, I see this error. Thanks for all your work!
  10. Generally speaking this isn't an issue with game containers as they can stop so quickly (within 15s or so). Do you have any specific examples?
  11. No problem, glad it was that setting and not something more messy!
  12. This is probably due to the fact that Docker containers are prevented from talking to the host by default. So the traffic will be trying to do this: You -> Tailscale tunnel -> Tailscale Docker on Unraid Host -x> Pihole container Before it was doing this: You -> LAN -> Directly in the network interface of the Unraid host and routed to the PiHole To fix, try going to Settings -> Docker and changing "Host access to custom networks" to "Enabled". You'll have to temporarily disable Docker to do this and then restart it. L
  13. It should just work, because I believe UnRaid IPv4 forwarding is on by default (it did and was for me). Try double checking with
  14. It's very strange that no image is output yet the whole VM still works, including VM use. I'm afraid I'm a bit stumped on this one. The only thing I can think of is perhaps you've left the VNC screen enabled, and the VM is setup to not output to the GPU screen?