Jump to content

bonienl

Community Developer
  • Content Count

    7779
  • Joined

  • Last visited

  • Days Won

    45

Everything posted by bonienl

  1. Yes, some are Windows VMs, and stopping them brings cpu load down. Thanks for the pointer. I see the high load already before using RDP, but may experiment a bit with the given workaround.
  2. I don't consider this a bug (more a feature request), but I'll make an update ... done
  3. There is nothing that Unraid can do to solve the issue. Have you tried Crucial and ask them?
  4. Your errors messages indicate something is wrong with the bz* files on the USB stick (maybe bad download). You can try to revert to the previous version (see Tools -> Update OS) And afterwards update again (make sure the USB stick is error free)
  5. Drivers are loaded from the USB device. Check your USB stick for corruption in a Windows (Mac) machine.
  6. Names in uppercase are sections and have an icon in front.
  7. Consistency, all title fields on the Dashboard page use capitalization.
  8. That's not possible. That's the easiest way to solve the issue. You should configure the 2nd NIC without IP address under network settings, and assign it to VMs
  9. Sorry for your OCD, but capitalized server names is per design.
  10. You can update in a single step, but need to make some precautions. Have a look at this
  11. After installing rc3 my cpu load is double to what it used to be. There are two processes constantly on high cpu load - node /usr/local - qemu-system-x86 Will do more investigation
  12. Another (minor) GUI update is the presence of the column "Cache" under Shares, which shows how cache is set for each user share. When WireGuard is installed, this is also reflected on the Dashboard, which gives a summary of the active and inactive tunnels. The network settings page has been revamped and allows to collapse sections, similar to what is done for WireGuard. Making better use of the available space.
  13. What happens when you disable WSD, see Settings -> SMB -> Enable WSD
  14. The default gateway is still your router (192.168.20.1) and VMs will still use that. The only destinations (remote peers) which go over the tunnel are the 10.253.0.X addresses.
  15. You are testing this from the client (peer) side, right? When you activate the WG tunnel, it will send ALL traffic over the WG tunnel because you have selected "Remote tunneled access", you need "Remote server access". Change the type of the second (and first) peer to "Remote server access". Next reconfigure the client(s) with the updated changes. You are thinking wrong
  16. What kind of VPN access are you configuring on Unraid?
  17. With SSL enabled, it requires DNS to work properly. If the DNS server is not reachable when the tunnel is active, it makes the GUI not reachable.
  18. Great interview @SpencerJ and good to see you @SpaceInvaderOne have more video plans. Perhaps all the cool new stuff in Unraid 6.8 is worthy of another video?
  19. It is fixed in Unraid 6.8.0-rc1. Just tested again, all fine.
  20. Local access should not be affected, no clue what you did. You can delete the files wg0.cfg and wg0.conf in folder /boot/config/wireguard using your ssh session. A "reboot" is required to restore.
  21. This plugin adds new pages to the GUI and certainly doesn't screw up the GUI. There MUST be something else in your system going on. You can manually remove the plugin: delete the file "dynamix.wireguard.plg" in the folder /config/plugins on your USB stick and restart your server.
  22. Unraid is not officially supported as VM, though it is possible to do. I don't know if anyone has such a set up, but in any case you will be on your own horses when troubleshooting.
  23. hehe, I created this functionality and should know what I have done 😁
  24. No, new information is appended to the existing log. With syslog rotation disabled, the log file will grow unlimited, or when syslog rotation is enabled, it allows a max file size and file count (.1 .2 .3 etc)