I guess it’d probably be a new UnRaid build and then copy the data into a new install.
If I use copy instead of Sync then I end up with lots of junk data over time and how would I know what needs to be restored. Would there be a point where I’d accidentally let RClone sync my empty shares to the cloud and wipe out my backup. Like if everything in my house were toast and I’m rebuilding new systems and trying to restore from RClone.
#Duplicacy unraid full#
One thing I’m trying to figure out is what a full restore would look like. RClone also doesn’t come with the same kind of versioning and deduplication that some of the GUI utilities do, but I suppose all that extra stuff is what limit is performance and reliability. Seems like RClone is more reliable but I don’t get the peace of mind of opening a docker once in a while and seeing that everything completed. You'll need to change the AllowedIPs line to have WireGuard start up properly.The thing with the GUI options is I get feedback like X GB to backup, 3 days remaining, last backup completed on, etc. It requires the following two changes.Ī change to your wg0.conf, due to a long lasting bug in WireGuard on these systems. Systems like Synology, Qnap or others with missing kernel modules can make use of this to establish a WireGuard VPN connection. This image includes wireguard-go, the Go implementation of WireGuard which runs in userspace. So don't give up too soon, it can all work eventually. All of a sudden after generating the 3rd config and also pasting in the ip found under My Fixed IPs, that seems to populate when doing a Port Forward Request, I managed to get port forwarding working. On the Netherlands server for example I didn't get any internet connectivity and at first I was unable to get port forwarding working on the Germany server. I had to click around quite a bit and finally after generating my 3rd config it worked. My experience with getting TorGuard working wasn't the smoothest journey to say the least. You will also have to add the additional environment variables TORGUARD_USER and TORGUARD_PASS or fill them in into the script directly (see curl command). #!/usr/bin/bash pubkey = $(grep PrivateKey " $ /api/v1/setup" This is an example of how your wg0.conf should look like. Why would you need this? Wanting to route traffic from other containers over the vpn is probably the most used scenario. Every port in this list will be blocked on the vpn interface, so that there's no risk that they might be exposed to the world via the vpn (mostly there in case your vpn provider screws up and piece of mind). If you need to expose additional ports you can use VPN_ADDITIONAL_PORTS, for example VPN_ADDITIONAL_PORTS=7878/tcp,9117/tcp. If for any reason there's a failure trying to setup ip6tables rules, you'll probably need to do sudo modprobe ip6table_filter on the host, this will mostly happen on systems that have ipv6 completely disabled. If your vpn provider supports ipv6 and you keep it enabled, you'll have full ipv6 connectivity over the vpn connection (confirmed with Mullvad). The WireGuard configuration should not have any ipv6 related stuff when ipv6 is disabled, otherwise creating the interface will fail.
The part with .disable_ipv6=0 can be removed or set to 1 if there is no need for ipv6, no attempt will be made in that case to set ip6tables rules and can prevent an error if the module ip6table_filter isn't loaded on the host. There needs to be a file wg0.conf located in /config/wireguard and you need to set the variable VPN_ENABLED to true for the VPN to start. This is probably not going to work if your OS has no kernel with WireGuard support. This image comes bundled with the alternative Web UI VueTorrent, to enable it you'll have to adjust your settings like pictured below. It should be in the format xxxx/tcp,xxxx/udp, take a look at the default with docker logs (variable is printed at container start) or docker inspect. Under certain circumstances it's required to run the WebUI on a different internal port, you can do that by modifying the environment variable WEBUI_PORTS accordingly.
0 kommentar(er)
