• 11 Posts
  • 42 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle


  • 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.


  • 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.



  • 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.




  • Not sure if it fits what you're looking for but I usually use YUMI for multi boot situations, can't recall it giving me any issues over the years. But I don't do anything overly complex either.

    Never had the need to use Ventoy myself so can't really give a good comparison but maybe others have used both & can give a better review.

    PS - For what it's worth my basic toolkit is YUMI with https://www.system-rescue.org and https://www.memtest.org, that alone covers the vast majority of my diagnostics/rescue situations. But I've also added Windows 10 ISO onto the multi boot on occasion which could be useful for getting to a Windows prompt with Windows tools when needed - though I have a habit of keeping Windows on its own USB via https://rufus.ie


  • Just a FYI all Lemmy instances have an /instances page where you can see instances it is linked to as well as blocked instances. For this one it is at https://lemmy.dbzer0.com/instances

    This instance does block instances for spam and suspicious/spammy behavior (dbzer0 admin also maintains https://fediseer.com).


  • Agreed, I don't care that much about that instance - but also mainly browse Subscribed posts in Lemmy so usually just view communities I'm interested & subscribed into. Other people should probably just do that, vs browsing All, if they're seeing too much in their feed they don't like.

    The real issue is that the Lemmy web ui & most apps/frontends don't support instance blocking as a user setting. Eventually when/if that's an option available to most Lemmy users this will become a non-issue.


  • When starting out here I ended up with a few accounts on different Lemmy/Kbin instances, interestingly the dbzero instance usually has the best overall performance/uptime from what I've seen. So no complaints here :)

    For what it's worth I'm usually on here via Tor & haven't had issues on dbzero, a lot of other Lemmy instances trip up over Tor connections and end up with crappy performance with Cloudflare/captchas/etc. or just block it outright.







  • Brickfrog@lemmy.dbzer0.comtoPiracy@lemmy.mlRarbg is back up
    ·
    11 months ago

    Misleading, rarbg.to still has the same shutdown message. The owners of rarbg would still have access to their own domain - if they intend to update it with any news they could.

    Any other pretend rarbg domain is going to be some copycat site trying to coast on the rarbg brand. Just like the copycat KAT sites that are around now, KAT itself is long gone too.