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.

Also, forgot to add that my previous dns server was not a docker container, it was a rasp pi running pi hole, in the same subnet, it had an ip of 192.168.1.14. I think maybe I have something wrong with how my docker is setup for networking

Done a bit more testing. For info, my unraid is in 192.168.10.0/25 and DNS Server 192.168.1.0/25, thus my traffic has to go via my router/firewall (which is a USG) to get between the networks. As such, I can do a tcpdump on the dest subnet interface (the 192.168.1.0 network) and if I do an NSLOOKUP from inside the docker container for something like Amazon .co.uk, I can see the request... 14:40:27.089533 IP 192.168.10.8.56750 > 192.168.1.11.domain: 23259+ A? amazon.co.uk. (30) 14:40:27.090166 IP 192.168.10.8.56750 > 192.168.1.11.domain: 23259+ A? amazon.co.uk. (30) 14:40:27.115705 IP 192.168.1.11.domain > 192.168.10.8.34893: 23259 3/0/0 A 54.239.34.171, A 178.236.7.220, A 54.239.33.58 (78) my 192.168.10.8 address is the unraid box, so I see unraid make a DNS request to my DNS Server 192.168.1.11, and I see my DNS Server respond back with the IPs, so the docker container is making the request by the look of it. if I then tcp dump by interface in the 192.168.10.0 subnet, where the unraid box is, I see the initial request go out (good, we see that also on the vlan where the DNS Server is) but I dont see the reply.

Yep thats looks fine from the GUI toolbar, same as an ssh session to the Unraid box itself. , can ping out to bbc.co.uk, and can also nslookup bcc.co.uk and it talks to the new DNS Server I have setup and resolves the name ok I tried from inside on of the dockers consoles and cant get a resolution... root@7d549749badd:/# ping bbc.co.uk ping: bad address 'bbc.co.uk' root@7d549749badd:/# nslookup bbc.co.uk ;; connection timed out; no servers could be reached root@7d549749badd:/#

sorry, did you mean from inside Unraid or the docker container itself?

hi, all seems to be fine from Unraid OS itself, nslookups happen from the CLI and reference the new DNS Server, and the docker containers im running that have dedicated IP's also seem to resolve OK, it just seems to be an issue with the containers sharing the Unraid IP with separate port numbers

Ive configured a new DNS server on my network - old server ip 192.168.1.14 - new one is 192.168.1.11. I stopped the array, changed the ipv4 DNS Server in the NIC to the new address, restarted the array, and now docker containers that are using the bridged network connection (serverIP:port number, such as sonaar, nzbhydra etc) can no longer perform DNS lookups. Ive rebooted the server, no difference, if I stop the array, and change the DNS Server back to the old address, start the array, it all works perfectly again. I tried deleting one of the offending docker containers, and reloaded it, along with a new config directory, still the same. Any ideas - have I missed a setting somewhere? Thanks

So this maybe an odd scenario I need to deploy VM's of firewalls to test, they only have a 30 day licence, and then have to be rebuilt. Is there a fast way of having everything configured as a template for one of these vm's pointing to an iso, so I can just click a few times, start one up and it builds - if these were physical boxes I was building, I could script the config so I have a baseline config (management IP dns servers, basic password etc) which I was hoping I could also use

Im getting this error about not being able to run the script, even though it still exists, im running it manually now and its running fine, but the scheduling bit of the plugin doesnt wanna find it for some reason? Event: Unraid Status Subject: VM Backup plugin Description: cannot run /boot/config/plugins/vmbackup/configs/Weekly_Backups/ Importance: warning 2022-05-22 04:40 User script file does not exist. Exiting.

Thanks. Will try it. Do you have number of backups and number of days both set?

Hi, having issues with the plugin removing old backups. I have number of backups to keep set to 2 at the moment. I have a Windows 10 VM, and this works perfectly, the script runs, backs up, and then deletes any other than 2 versions, no problem - the file type is .img. I have 2 other VMs, LibreNMS which is also a .img file, and Home Assistant which is a qcow2 file. When the backup runs, it deletes all the config related files for any backup over 2, but doesnt actually remove the disk image, so im left with manually having to clear out just the disk images. Ive pasted the log from the last back-up job, and highlighted this... 2022-05-08 06:05:47 information: backup of /mnt/user/vms/librenms/old_librenms-ubuntu-20.04-amd64.img vdisk to /mnt/user/sysbackup/vms/autobackup/LibreNMS/20220508_0440_old_librenms-ubuntu-20.04-amd64.img complete. 2022-05-08 06:05:47 information: the extensions of the vdisks that were backed up are img. 2022-05-08 06:05:47 information: vm_state is shut off. vm_original_state is running. starting LibreNMS. 2022-05-08 06:05:48 information: backup of LibreNMS to /mnt/user/sysbackup/vms/autobackup/LibreNMS completed. 2022-05-08 06:05:48 information: number of days to keep backups set to indefinitely. 2022-05-08 06:05:48 information: cleaning out backups over 2 in location /mnt/user/sysbackup/vms/autobackup/LibreNMS/ 2022-05-08 06:05:48 information: removed '/mnt/user/sysbackup/vms/autobackup/LibreNMS/20220424_0440_LibreNMS.xml' config file. 2022-05-08 06:05:48 information: did not find any nvram files to remove. 2022-05-08 06:05:48 information: did not find any vdisk image files to remove. So the backup says it cant find a disk image to remove, but looking in the directory, its there...(24th April 2022) -rw-r--r-- 1 root root 20G Apr 24 05:47 20220424_0440_old_librenms-ubuntu-20.04-amd64.img -rw-rw-rw- 1 root root 6.4K May 1 05:39 20220501_0440_LibreNMS.xml -rw-r--r-- 1 root root 20G May 1 05:44 20220501_0440_old_librenms-ubuntu-20.04-amd64.img -rw-rw-rw- 1 root root 2.6K May 1 05:44 20220501_0440_unraid-vmbackup.log -rw-rw-rw- 1 root root 6.4K May 8 05:59 20220508_0440_LibreNMS.xml -rw-r--r-- 1 root root 20G May 8 06:05 20220508_0440_old_librenms-ubuntu-20.04-amd64.img -rw-rw-rw- 1 root root 2.8K May 8 06:05 20220508_0440_unraid-vmbackup.log Any ideas why its happy with the Windows 10 backup, sees the img file, and deletes anything older than 2 files, but won't do this for LibreNMS (and the qcow2 for the other VM) but does delete all the other data older than 2 for the other vms? Thanks 20220508_0440_unraid-vmbackup.log