• 1 Post
  • 5 Comments
Joined 4 months ago
Cake day: July 2nd, 2025
  • BremboTheFourth@piefed.caOPtoPiracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com•Can't seed a new torrent unless the leech is also listening on an open portEnglish
    2·
    2 days ago

    I’m not familiar with ProtonVPN configuration so can’t guide you much there, presumably if the port forwarding option only allows for one setting then maybe it’s doing both TCP/UDP? I dunno…

    Maybe that’s a good place for me to do some digging, but this is an issue specific to the new torrent I made. Things I download first seed just fine, and at much higher rates when I have the port open, so I think that’s working normally regardless of any TCP/UDP stuff under the hood.

    can the test torrent client see that there is a seed on the torrent?

    I think I misread this. No, neither client sees any peers, but when viewing the trackers within the client, the trackers are reporting peers. I’ll keep what I originally typed in the spoiler below.

    Tap for spoiler

    Yes. Incidentally, when I opened the port on the leech client, a few other leechers joined the swarm as well, but I was only ever able to upload anything to my own test client. Even once the upload finished, neither client uploaded anything to those other leechers either. A few hours later, the count (looking from both seed and leech client) went back down to 1 seeder and 1 leecher.

    Um. Just out of curiosity, I checked the peer list again, and while I’m still the only leecher, some of the trackers are now showing multiple seeders? I definitely only ever uploaded anything to myself, how is that possible?

  • BremboTheFourth@piefed.caOPtoPiracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com•Can't seed a new torrent unless the leech is also listening on an open portEnglish
    3·
    2 days ago

    Always good to double check, but yes, I used canyouseeme and the port is definitely open.

    The port is configured through ProtonVPN. A few menu options below the one for port forwarding there’s another for configuring the connection as OpenVPN(TCP), OpenVPN(UDP), or Wireguard. I’ve had other issues in the past and Transmission’s internal port testing thing always specifies it’s testing TCP, so that’s what I had it set to with Proton. I switched Proton to UDP and am waiting a few minutes before testing it with Wireguard.

    lol well with Proton’s Wireguard config it doesn’t seem like I can open a port at all, so I’ve set that back to TCP for now.

    Could I be missing a step with the trackers? Do I need to upload something to them first? I looked around on opentrackr.org and didn’t see anything, plus in the client the trackers are reporting 1 seeder (me) and leechers, plus it worked when I opened the port on my test leech… I’m so lost :(