Magnet links on Readynas not working

[hufggfg]

Hi there, hoping someone can help me.

Have just installed Transmission on my Readynas, and added a couple of Torrents which seem to be working fine.

I can't however get it working with Magnet links, clicking a link in a browser effectively seems to do nothing.

Got to admit i'm not a particularly advanced user, so a simple explanation of what i may need to do/try would be much appreciated.

Thanks

p.s. I'm using Chrome if that makes any difference.

[moonman]

You may want to install Transmission-gui that will associate itself with magnet links.

[darrenbest]

You may want to install Transmission-gui that will associate itself with magnet links.

Indeed, doesn't matter if your workstation is Windows, Mac, or Linux, the Transmission Remote GUI (http://code.google.com/p/transmission-remote-gui) is a cross-platform interface to Transmission. Chrome will automatically recognize the "magnet://" link type, and provided "Remote GUI" installed as the default app for magnet links (it should do that when it is installed), the new program will launch when you click the link. Just configure it to point to your ReadyNAS' "watch", "incomplete", and "complete" folders, and your Torrents will load. Plus, you'll have a "uTorrent-like" interface to boot.

[hufggfg]

Thanks.

I've got the remote gui up and running, connected properly, but the magnet links still aren't working. Clicking them does nowt.

Just realising that in my original message I never actually said I was running a mac... oops sorry about that, I am running OSX...

I have also tried using Safari just to see if that made a difference, and that way just brings up a page saying "Safari can't open the specified address"..."Mac OS X doesn't recognize internet address starting with "magnet"".... this doesn't sound right...

Any help much appreciated!

[blacke4dawn]

Technically speaking, since you aren't using Transmission itself to "read" the magnet links but a third party product then there is nothing that the Transmission devs can do about it, so I would rather take this to the one who makes the gui you use to communicate with your transmission installation.

[rb07]

I agree with blacke4dawn, which in other words is saying: magnet association is something the transmission-daemon doesn't do.

To be clear, usually you have 3 choices to handle magnet (and torrent) association: you either let the application installer do it, you let the application do it, or you do it yourself.

With the daemon running on a NAS there is obviously no installer and no application on your Mac, so options 1 and 2 are out of the picture. Unless, like moonman and darrenbest suggested, you install something else which again could add the magnet association; but their suggestion was for Windows, I have no idea if there's something for the Mac (does Transmission-Mac handle remote sessions?).

Then there is the third choice: do it yourself. I don't use or know Mac OSX, but from the experience of building an installer for Transmission-Qt for Windows, I can tell you there are 2 ways: at the OS level, and at the browser level.

Both need an application to use... most of the time. There is (or was) a Firefox plugin to send the torrent/magnet to the daemon using RPC (I don't use it and I don't know its current state, but check Transmission's add-ons page, the plug-in is the last item on the list); perhaps there's something similar for other browsers.

[blacke4dawn]

@rb07
There is one remote GUIs that run on Windows, Mac and Linux: Transmisson Remote GUI (note the misspelling of transmission), which the OP is already using. Last time I checked it it was associating itself with magnet links, but that was on Windows so not sure if that app/installer has problems with Mac OSX.

[rb07]

There are several with "remote" and "multi-platform" on the add-ons page I pointed out.

Don't answer to me, I'm not the one looking for solutions, I don't have the problem.

[cfpp2p]

for

-Ubuntu 11.04
-Chrome 17.0.963.78
-transgui 3.2


http://code.google.com/p/transmisson-re ... ?id=521#c1

[MrAsker]

My problem is slightly different.

I have the "Transmission Remote dotnet" Client and it connect fine to Transmission and when I click the Magnet Links they are handled by the Client and I can see in the WebGUI and in the Client that the Transmission Daemon get the Magnet Link but then nothing happens. I can't seem to get any Magnet Link based downloads to actually download.

In the Transmission Preferences I have uPT, PEX and DHT enabled, which I've understood are requirement. I have a range of BT ports specified in the settings.json file, randomly choose one of them when Transmission starts, have the same range of port forwarded in my Netgear WNDR3800 router to my ReadyNAS NV+ and I can see with "netstat -an | grep [port range]" on the NAS that the forwarding works. Still no downloads.

I've tried turning of uPT, restarting, choosing different Magnet Links, etc .. Still no Download.

So then I look in the /var/log/daemon.log file, grep for DHT and see a bunch of these rows:

Code: Select all

Mar 21 10:24:59 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E16+Virgin+Territory+HDTV+XviD-FQM+[eztv] Starting IPv4 DHT announce (poor, 16 nodes) (tr-dht.c:574)
Mar 21 10:29:56 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E12+HDTV+XviD-LOL+[eztv] IPv4 DHT announce done (tr-dht.c:542)
Mar 21 10:29:56 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E04+720p+HDTV+X264.mp4 IPv4 DHT announce done (tr-dht.c:542)
Mar 21 10:32:19 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E16+Virgin+Territory+HDTV+XviD-FQM+[eztv] IPv4 DHT announce done (tr-dht.c:542)
Mar 21 10:32:19 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E08+HDTV+XviD-LOL+[eztv] IPv4 DHT announce done (tr-dht.c:542)
Mar 21 12:11:04 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E18+HDTV+x264-LOL+[eztv] Starting IPv4 DHT announce (poor, 16 nodes) (tr-dht.c:574)
Mar 21 12:18:38 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E18+HDTV+x264-LOL+[eztv] IPv4 DHT announce done (tr-dht.c:542)

So then I grep for [Name of the TV Show] and get A LOT of these:

Code: Select all

Mar 21 16:12:21 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E09+HDTV+XviD-LOL+[eztv] Connection failed (announcer.c:990)
Mar 21 16:12:21 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E09+HDTV+XviD-LOL+[eztv] Retrying announce in 7247 seconds. (announcer.c:999)
Mar 21 16:12:21 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E15+HDTV+XviD-LOL+[eztv] Connection failed (announcer.c:990)
Mar 21 16:12:21 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E15+HDTV+XviD-LOL+[eztv] Retrying announce in 7227 seconds. (announcer.c:999)
Mar 21 16:13:35 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E02+HDTV+XviD-LOL+[eztv] Connection failed (announcer.c:990)
Mar 21 16:13:35 ODDJOB nss_wins[32216]: [Name of TV Show]+S03E02+HDTV+XviD-LOL+[eztv] Retrying announce in 7243 seconds. (announcer.c:999)

Any ideas? Any suggestions as to what to try next? Any suggestion as to where to look for more info?

Please help me, I'm running out of ideas and options. I guess if I can't get this to work I have to set up a uTorrent client on a "server" instead of using my NAS for the BT/MagnetLinks DL:s. But where is the fun in that?

[rb07]

I have uPT, PEX and DHT enabled, which I've understood are requirement

No, they are not a requirement. Some magnet links may require DHT, but that's it.

Your log has nothing unusual. Nowadays its normal that torrents have bogus trackers (those that will never send a response, because they don't even exist), overloaded trackers (those that some time don't respond), errors, blocks, ... you name it.

You need to analyze the problem starting with one torrent: does it have information from any tracker? does that information include seeders and peers (or is it all zeroes)?

One thing you got wrong is port mapping, trackers don't use the peer port, which is what you were talking about. Trackers use port 80, or whatever port they have in their URL; and you don't need to open that port, because the client initiates that communication. But in case you have a very restrictive firewall (or badly configured), and all your trackers show no connection (you see either the error message, time-out, or no-response), then try testing them by hand (get the URL and use it with curl, or the browser to see if something comes back, or is it all time-outs) -- of course you can only test the HTTP trackers, not the UDP trackers... which brings a BTW: what version of Transmission are you using? because UDP tracker support only works since version 2.30, and currently many trackers are UDP only.

[MrAsker]

Thanks for your reply. I see I was not clear so I'll see if the below is giving more insight into my problem(s).

Thanks for the clarification regarding DHT. I did know it is not a requirement for all Magnet Links, I meant it is a requirement to have it enabled since some Magnet Links require it to be enabled. But more importantly I guess it is no downside to having uTP, DHT and PEX enabled, or?

I do understand the different between connecting to Trackers and connecting to "peers". However I think you just gave me a new idea anyway so I'll check if I can see why I can't connect to some peers and get back to see if your/my theory is correct. My problem is not really connection to the tracker but actually I guess the peers. I don't seem to get good or any connections to any peers. Even if I have thousands of peers for a specific torrent. Anywhere this is or can be better logged somewhere?

I'm using Transmission 2.42 for ReadyNAS:
http://www.readynas.com/forum/viewtopic ... 47&t=24271