erak

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

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

erak's Achievements

Noob

Noob (1/14)

7

Reputation

  1. I've been running unraid for about a year and I think this has happened almost every time, therefore I thought it was by design for some reason. Not using legacy, T600. Updated today from 6.12.2 to 6.12.3. I think I waited for the ok, but now I can't say for certain. But I usually do, and the version type change has happened anyway. server-diagnostics-20230812-1909.zip
  2. Why does it change driver version to "latest" after a system update, even if I had previously chosen "Production Branch"?
  3. I updated to 6.12.2 from 6.11.5 two days ago, and I just had the same issue. "Execution error" when trying to start a container. Restarting docker didn't work, CPU started to go nuts, had to reboot the server. If it's related to containers with special network settings as above I would suspect "binhex-delugevpn". I'm not running that much, no VMs. micro-8-diagnostics-20230705-0023.zip
  4. There are several ways, I used vi. Open terminal and write the following and press enter: vi /etc/wireguard/wg0.conf Press i to edit, do your changes. Press esc to exit input mode. Press : to enter a command, write wq and press enter, which means "write and quit".
  5. I haven't tested if too many spaces is an issue. But standard is one space before "table 200". Now you have double and triple spaces.
  6. Thanks for this find. I had the same issue after updating. After removing " dev " from line 12 and 15, and "dev wg0 " from line 11 it's up and running again. These are the exact differences from the old configuration.