Yeah I have issues with my home setup at least that often. I can only think of two occasions where the solution took more effort than a reboot. Maybe we’re all just old enough for “every 6 months” to feel like every 5 mins
To clarify, by “issues” I mean “system stoppages not precipitated by me fucking with something.” I screw up my own system way more often than that lol
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.
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?
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 :(
“Ah but you see, it’s not misleading at all! You really are purchasing a temporary license to watch the content!”
Considering how much leeway we give food companies to lie about how they label their products, I have absolutely no faith we’ll correct the advertising here either
In a similar boat, I’ve thought about that but if I ever upgraded to a stronger real centralized PC I’d have to do a bunch of Docker setup and if anything breaks my whole system would go down. As it is, with piecemeal shitass laptops each running individual services I get lots of redundancy!