(Solved) Terrible seeding to private tracker since trying and reverting port change

[mara7honman]

I'm seeding a lot of torrents, about 1600, almost entirely on a private tracker, but wasn't super happy with the speeds I was getting. So I tried changing the port away from the default, just in case my ISP does some sort of limiting on 51413. Made sure that the new port was forwarded properly first, and had that and the original port both forwarded at the same time, then made the change. Noticed that my upload speeds reduced to almost nil, I decided to revert back to the initial config. Unfortunately, I seem to be stuck with almost no uploads, even after switching back. On the other hand, download speeds don't seem to have been affected at all.

So it looks like I can connect to peers to leech from, but peers seem to drop even if I can upload to them.

I'm using OPNsense running on way over-provisioned hardware, doubt that the router performance is the source of any limitation. The OS is MacOS 12 running as a VM on an ESX box, which is definitely a bit of a weird setup, but has worked in the past.

Things I've tried:
-Restarting every component in the chain, individually and at the same time, pausing all torrents, restarting them etc after any change
-Looking at only recent torrents on this private tracker
-Shutting down any IPS/security system on my router that might be interfering with peer connections
-Turning on and off NAT-PNP
-Rolling back the version of Transmission, also upgrading back to the current one
-Downloading a public torrent, a ubuntu build, had better seeding, but nowhere near what I expected
-Installing latest OPNsense version

At this point I'm wondering if the problem lies in the tracker/swarm, somewhere in the router/firewall, or perhaps some kind of bug in Transmission itself.

I don't want to blindly create an issue on github without properly investigating first. I'm hoping that someone on the forum might've seen a similar issue at one point, or could offer some suggestions in what else to test.

[mara7honman]

Figured this one out. Turns out that most of my transfers were set to accept 0 peers. I don't remember setting that, but it's possible that I fat fingered a setting somewhere. All working now.