brickfrog

Should be fine, just don't cheap out on the external drive / cable you will be using. And when you're using something like smartctl you'll know right away if SMART info is passing through your USB for proper testing.

I've done a lot of these type of scans via USB drives, honestly the more annoying part is that some USB drives do wonky things like go into sleep mode within 1-5 minutes which will disrupt any sort of scanning you had going. So with USB drive scanning I usually implement something to keep the drive alive and awake e.g. a simple infinite loop script to write a file every x seconds, or if you're on windows you can also use KeepAliveHD.

however I can still seed the torrent how is that possible?

Yes you can still seed as well as download. But you are limited and can only upload and download torrent data in swarms that contain peers that are themselves fully connectable (port forwarded).

So say you join a torrent swarm that only contains peers just like you (firewalled, no ports forwarded) then no one will transfer any torrent data with each other. Everyone is stuck waiting for a fully connectable (port forwarded) peer to join that swarm.

FYI all the official domains and .onion link are on their proxygalaxy page

https://proxygalaxy.me

For what it's worth .to does not forward me to .mx, each of those domains seem to work fine on their own. Not sure what exactly is happening with your browser, maybe try clearing the cache / doing a hard reload.

Hmm just tried it & it doesn't load either. The last official onion link I found published on https://proxygalaxy.me (via archive.org) was in May 2024 at http://galaxy3yrfbwlwo72q3v2wlyjinqr2vejgpkxb22ll5pcpuaxlnqjiid.onion but it doesn't seem to load for me in Tor Browser.

I tried creating my own torrent and was able to dl it on another device, but on her machine it stayed at 0% and wouldn’t let me connect to seed

At least one of the torrent clients needs to be fully connectable (port forwarded) for torrents to transfer data. You need to test that e.g. test your torrent client's incoming connection port with a port test website like https://www.canyouseeme.org, https://www.yougetsignal.com/tools/open-ports, etc. & make sure those port test websites can successfully test connect to your torrent client's incoming connection port. If the test fails then you need to look at opening the port via your OS firewall and/or router firewall.

Is FTP a good option? I set up a proxmox server last night but I don’t really know what I’m doing yet

Probably best to avoid FTP if you don't know what you're doing, it's not all that secure.. you'd want to at least configure SFTP or FTPS which is just going to be more complicated vs fixing your torrent issues. And technically you still need to make those connectable (port forwarded) too, just like your torrent client.

All that aside it's probably easier to use Syncthing if you can't get the torrent working.

You could also try one of those file transfer websites that use WebRTC to transfer data peer to peer e.g. https://file.pizza or similar. Not sure how well they work for huge amounts of data but their github page mentions that Firefox is better for that, apparently Chrome starts to choke with data 500+ MB.

Nowadays I buy digital music (mostly via Bandcamp but there's also HDTracks, Qobuz, etc.) & play the music that way. Can also stream my own music library if I want via Jellyfin or other applications.

re: physical CDs, yes I've got a ton of those too from before you could buy digital music but have already ripped them. Haven't had a need to touch the physical discs in years but still keep them in CD binders just in case.

Also not sure if it matters but for me I'm always living in small apartments/rooms so I absolutely avoid collecting physical items, there's just no space for that.

You might be confusing public IP addresses with ports? If your torrent client doesn't have a public IP address that just means it's offline / no internet. Maybe your internet is down or the VPN is disconnected. You're won't torrent anything at all in that state.

One side of the connection needs a ~~public address~~ open port, not both. When both parties don’t have a ~~publicly addressable IP~~ open port, ~~the status is firewalled. I guess~~ they can "see" each other but are unable to exchange any torrent data.

For what it's worth in the situation where both peers don't have open ports (meaning they are both firewalled) they end up having to wait for another peer to join that torrent swarm that happens to have a open port, that's the only way any data will exchange in that swarm. Until that happens those two peers will sit there waiting and not exchanging data.

So your saying it should have never worked even if I was not using docker?

Correct.

Also it’s now working… I have no idea

Yeah that's weird, I don't know if you accidentally found a way to hack Windscribe into temporarily giving you a port forward on their free plan. But otherwise you do need to be a paid member on their Pro account for that feature.

Or it's just going to randomly stop working again.

Is there a way to actually test your port forward within Docker? I'm not familiar enough with that configuration to suggest anything but maybe someone else knows about that. Usually without Docker I'd just start up the torrent client & then use a web browser with any port test website (https://www.canyouseeme.org, https://www.yougetsignal.com/tools/open-ports, etc.). But for Docker not too sure how to go about that.

Mullvad does not have port forwarding so it would be normal for your torrent client to be firewalled.

I'm not too sure why you & OP sometimes see it as temporarily connectable when changing/randomizing the incoming port when the VPN service never provided you an open port forward.

I have never done any kind of manual port forwarding my current VPN provider does not do that at the price I have it for right now.

If the VPN provider does not support port forwarding then it is normal and expected to always be firewalled. Toggling random ports doesn't change that fact.

Not sure why you would sometimes see your status as fully connectable, guessing either it's a Windscribe misconfiguration when you initially connect (?) or qBittorrent gets confused during the intitial connect. Or there's some other misconfiguration.

You might want to see if other people using that VPN provider have more insight, maybe they are doing something strange with the ports when you initially connect & eventually close them on you.

True, wouldn't be too different vs just using a VPN. You're choosing to trust the Tribler tech and the Tribler exit node operator vs choosing to trust the VPN provider. Granted most VPN connections are going to have much better performance vs anything Tribler related.

There is a nice side effect of running an *arr stack against Tribler, even in 1 hop mode - Your Tribler node is much more easily pulling in new content into the Tribler network for other users to access afterwards without needing an exit node. Ideally it's just one Tribler node/user needing to pull data through the exit nodes while the rest would just pull it from you and share with other nodes in-network.

Torrents over I2P work the same way. If the torrent data isn't found within I2P and you have outproxies configured you could pull torrents from the clearnet & afterwards other I2P users just share amongst the I2P network.

That's pretty cool, thanks for sharing! Been a while since I tried it out but last I looked Tribler's own automation features were quite lacking so something like this helps a lot.

I was not able to download anything with more than 1 hops in between - ie it does hide your real IP address, but only uses one relay in between.

Hmm I don't think there's any relays at all in that configuration, unless you're counting the exit node itself?

https://github.com/Tribler/tribler/issues/3067#issuecomment-325367047

One thing to keep in mind is that to download torrents from outside Tribler's own network you would need to download through an exit node.. not sure on the exact stats but last I tested exit nodes were only like 5-10% of the Tribler user base. For a while I tried volunteering my own VPN connection as an exit node for Tribler just to see how it went but the Tribler client kept locking up/crashing after a few days so the experiment did not go well.. hopefully works better nowadays.