rorton

cheers, I thought I'd give it a go, its installed no problem, but got this message in the output: WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.

Just popped in to say thank you, tried this today and worked perfectly, restored data and im up and running, very simple. I was looking at interest with the comments around the newer devices - sorry if this is taking the subject off topic - im also looking at a UXG Lite, but I have a config.json file running on my current usg3p to set certain things - IGMP Proxy for IoT devices on different vlan, and WAN DHCP Option 61 for SKY vdsl auth - unsure if these will work or there is an alternative to add this stuff into the newer devices. Assuming the config.json is gone now

That makes sense actually. I run adguard in a docker for all my network dns so I bet that my unraid it reaching out to the internet when there is no dns available till the docker is up

no problem, thanks for the reply though, much appreciated

I do have this in my syslog too... Aug 3 21:08:40 Unraid root: plugin: installing: vmbackup.plg Aug 3 21:08:40 Unraid root: plugin: creating: /boot/config/plugins/vmbackup/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz - downloading from URL https://raw.githubusercontent.com/jtok/unraid.vmbackup/master/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz if I then delete the plugin, and then reinstall, I see this in syslog... Aug 3 21:24:51 Unraid root: plugin: creating: /boot/config/plugins/vmbackup/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz - downloading from URL https://raw.githubusercontent.com/jtok/unraid.vmbackup/master/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz Aug 3 21:24:52 Unraid root: plugin: checking: /boot/config/plugins/vmbackup/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz - MD5 Aug 3 21:24:52 Unraid root: plugin: running: upgradepkg --install-new /boot/config/plugins/vmbackup/packages/xmlstarlet-1.6.1-x86_64-1_slonly.txz Aug 3 21:24:52 Unraid root: plugin: creating: /boot/config/plugins/vmbackup/vmbackup-v0.2.5-2022.12.25.txz - downloading from URL https://raw.githubusercontent.com/jtok/unraid.vmbackup/master/vmbackup-v0.2.5-2022.12.25.txz Aug 3 21:24:52 Unraid root: plugin: checking: /boot/config/plugins/vmbackup/vmbackup-v0.2.5-2022.12.25.txz - MD5 Aug 3 21:24:52 Unraid root: plugin: running: upgradepkg --install-new /boot/config/plugins/vmbackup/vmbackup-v0.2.5-2022.12.25.txz Aug 3 21:24:55 Unraid root: plugin: vmbackup.plg installed

sorry, I may have been assuming what @CodeGlitcher was experiencing was the same, is it is sort of uninstalling itself. My issue is that when I reboot, the box comes up and the plug-in sits in the Plugin file install errors (as image) If I delete and then manually install again, it works. I have just rebooted to get the screenshot, if there are any logs I can provide from anywhere please let me know Im using 6.12.3, and has been happening on all 6.12 versions

Just to say I have the same problem. Any time I reboot my server, this plugin appears n a list of plugins with errors. I can delete the plugin, reinstall and it works perfectly till the next reboot.

What ive just done, is build an Ubuntu VM and set this up as a VPN Server if you like, Its running Ubuntu server, and at the moment, I have a wireguard vpn connection to NORD VPN. My Ubuntu VPN VM has 2 interfaces, an external (going to the internet) and an internal (facing the network) and what I did, was changed the default gateway of the devices I want to go over the VPN to be the internal IP of the VPN VM, and my other devices have a normal default gateway and go out to the internet normally. Works well.

im struggling to get this to run. In my docker container log , I get the below... [2022-08-14T23:40:43+00:00] Enabling connection to eth0 192.168.1.9/25 [2022-08-14T23:40:43+00:00] Enabling connection to secure interfaces [2022-08-14T23:40:43+00:00] No interface network6 detected [2022-08-15T00:40:43+01:00] Enabling connection to network 192.168.0.0/16 [custom-init] no custom files found exiting... [ls.io-init] done. [2022-08-15T00:40:43+01:00] Finding the best server... [2022-08-15T00:41:40+01:00] Unable to select a server ¯\_(⊙︿⊙)_/¯ My docker command that runs.... root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='nordlynx' --net='br0.1' --ip='192.168.1.9' -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Unraid" -e HOST_CONTAINERNAME="nordlynx" -e 'PRIVATE_KEY'='MYKEYHERE' -e 'QUERY'='' -e 'NET_LOCAL'='192.168.0.0/16' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://s1.nordcdn.com/nordvpn/media/1.1527.0/images/global/logos/square/nordvpn-48.svg' --cap-add=NET_ADMIN --sysctl net.ipv4.conf.all.src_valid_mark=1 --sysctl net.ipv6.conf.all.disable_ipv6=1 'bubuntux/nordlynx' 042fa609105b4556acdc6d57fb5229c82e2d1a3694aa221d608554fdf55f105c

I did think that, but I have a USG and apparently the throughput really takes a hit

Is it possible to set this up to allow other hosts on your network to use the wireguard vpn for their traffic? for example, I have. Few smart tvs and fire sticks I’d like to send their traffic over a vpn, but everything else on my network to go out via my normal isp to the internet?

I did a backup of my config and went for the upgrade - all seemed ok, it did its usual upgrading database thing when it started up, but all running so far.

thanks, thats a great idea!

Ive resorted to giving each of my docker containers a dedicated static IP address instead of sharing the hosts address and it all works now so will mark this as resolved

thinking about this then.... I have an Unraid Server in 192.168.10.8 with a number of docker containers running on separate ports. One of these docker containers needs to make a DNS request, so another docker container in a different subnet 192.168.1.11 The request leaves 192.168.10.8, I see this in a tcp dump, gets to the router/firewall, and then leave the router/firewall on the 192.168.1.11 interface, dns does its thing, gives an IP address back, this gets to the firewall, then nothing happens, I dont see the packet again at the firewall. Now, if I have a host in the 192.168.10.0/25 network, like my Mac for example, I can make and resolve dns no problem at all with the docker container.