Transmission

Your problem is that you don't know much about networks[1]... you can't just start bittorrent clients on your LAN and expect them to work with each other (i.e. they all share the same WAN IP address, and unless you changed the configuration all transmission clients will use the same peer port, and w...

The peer port has nothing to do with your problem. The real problem seems to be with magnets, please confirm (i.e. regular .torrent files work). If a magnet stays in the "retrieving metadata" stage, then you have to look at the magnet: does it have tracker info? or is just a hash code? If ...

Nothing strange. Your torrent is not registered with that specific tracker, that's the reason the tracker responds with the "not found". Other peers still are able to find the torrent through DHT (a.k.a. tracker-less), they just use the hash code of the torrent and ask other peers (i.e. th...

set it so after a specific ratio of a file, it automates to change it's directory, stop seeding, and remove the torrent file from the listing. Yes. Use a script. You'll have to write the script, and run it from cron. The "stop seeding" part should be in Transmission (as the torrent's rati...

You are using it wrong. If you have a ~/.netrc, then just run transmission-remote -l If you don't have that file, or want to use another, then run transmission-remote -N <other-file> -l The "invalid option" message was referring that you didn't put the file parameter (<file> on the help ou...

Is it the tracker that sets this ratio limit? No. Trackers have nothing to do with this... besides, you are showing a torrent specific setting, so there was something that did that, probably the same "thing" that loaded the torrent. The real questions are: what exactly do you use? (i.e. T...

What do you mean by my attempts at manual port forwarding are disabled Of course the important part are those "forwarding failed with error 718" which looking at the UPnP code mean... * 718 ConflictInMappingEntry - The port mapping entry specified conflicts * with a mapping assigned previo...

Do you think I should compile it from sources? No, not for the specific problem you're reporting. Is that ratio limit (15.0) general, or specific to one torrent? Because we have overlooked that a torrent could also have its ratio limit set, and that value is not in settings.json, but in the torrent...

Version 2.52? I was talking about the current version, I don't remember about a version that old (almost 2 years), and perhaps the problem you describe is one of the many that have been fixed. The response seems to show memory problems (the response string concatenated with something else)... but th...

Does settings.json has any syntax errors? (you ended without showing the actual ending, a line with closing curly bracket: }, if its not there, then you have a syntax error and your configuration is invalid). Are you looking at the correct settings.json? Ask the daemon in what directory is the corre...

Have you tried a "second opinion"? Like the canyouseeme link on the "PortClossed" article... The port test server is not down, it works fine for me, but it could verify that you do have a double NAT, or other (firewall on server) problem. Is the log from the server? The "Got...

No bits used.

The speed units by default are SI (multiples of 1000) and bytes, except on the unofficial Windows port where the units are (configurable but by default) IEC (multiples of 1024) which is what Windows uses.

The problem is not the creation, or the other steps you're showing. The problem is how the peers see (or not see) your seeding machine... First: Is your peer port open? (i.e. mapped to the seeding machine). If you test inside a LAN, then it usually won't work, the tracker sends your WAN IP address t...

Could seeding happen even if the port is closed? Yes. "Port closed" really means "server not responding on that port from outside". The port is not really closed, just not mapped (even if you use UPnP, that doesn't mean that it was successful mapping the port -- you may need to ...

jahutchi:
If you can build Transmission you could help by testing the change I proposed in #5583 (and reporting on that ticket the results).

I've already tested it (long ago) for a similar problem in Windows. I would expect that it should also solve the problem you are seeing.