Droolio

Suppose one way around it would be to rent a cheap VPS in the UK and piggy back off the connection?

Otherwise, there’s a s2 ‘NORDiC’ version going around which is actually in English audio - just with various scandiwegian soft subs, so it’s defo out there. DM me if you still struggle to find it.

More people should use BiglyBT and its Swarm Merging feature. You get the ability to seed or download chunks from peers across separate torrent files.

It’s a shame because if more people used it, the BiglyBT devs might add hash-based merging (with v2 torrents) instead of just size-based. Hybrid/v2 merging is still possible, but file size is less reliable and caters to files only larger than 50MB.

Some kinda auto v1/v2/hybrid private<->public torrent maker plugin for BiglyBT would be… bigly.

If qBittorrent/qb-nox is bound to your VPN interface, then 1) your VPN needs to support port forwarding, and 2) forwarding a port on your router is pointless and unnecessary. Your only way around it is to switch VPN or don’t use VPN and then port forward.

Actually, ufw has its own separate issue you may need to deal with. (Or bind ports to localhost/127.0.0.1 as others have stated.)

The next best alternative would be BiglyBT’s Swarm Merging feature (which works similarly, and amazingly well on v1 torrents considering it only stores a precise file size instead of a hash in Vuze/Bigly’s own DHT). I’ve been able to ‘complete’ numerous separate torrents where availability was <1.

BiglyBT already supports v2 but dunno if Swarm Merging works with such torrents yet.

Thank you for posting this, hadn’t heard of it before.

Yes, I also work in IT.

The paid GUI version is extremely cautious on the auto-updates (it’s basically a wrapper for the CLI) - perhaps a bit too cautious. The free CLI version is also very cautious about making sure your backup storage doesn’t break.

For example, they recently added zstd encryption, yet existing storages stay on lz4 unless you force it - and even then, the two compression methods can exist in the same backup destination. It’s extremely robust in that regard (to the point that if you started forcing zstd compression, or created a new zstd backup destination, you can use the newest CLI to copy data to the older lz4 method and revert - just as an example). And of course you can compile it yourself years from now.

The licence is pretty clear - the CLI version is entirely free for personal use (commercial use requires a licence, and the GUI is optional). If you don’t like the licence, that’s fine, but it’s hardly ‘disingenuous’ when it is free for personal use, and has been for many years.

IMHO, Duplicacy is better than all of them at all those things - multi-machine, cross-platform, zstd compression, encryption, incrementals, de-duplication.

Wouldn’t you be on CGNAT though? How are they blocking it - at the DNS level? Have you tried a CNAME record that points your own domain to the actual duckdns domain? Just curious how/why they might be doing this.