Transmission

Hi there, total n00b here, so sorry if this has been covered. I did my due diligence and searched the forum, but could not find a solution.

Anyway, running Transmission 1.76 (9392) on a Mac Mini OSX 10.6.2 - and when I access the web ui, it gives me data fine, but if I try and upload - by copying a URL for a .torrent file from my favorite tracker and pasting it there and hitting 'Upload' -- nothing happens. No error message even, just nada. Tried several trackers, and a couple of browsers, no success on that front.

Help?

I have exactly the same problem. Doesn't seem to be the first one. But last Bug report got closed it seems...

Its normal that when a tracker enforces that you log-in to download the .torrent file it won't allow the Web client to do the download (since the Web client doesn't do log-in or present any cookies or whatever to show the request came from a legitimate user).

Also is normal for the Web client to not show any error message, in this case it received an "access denied" response which to the Web client looks nothing like a .torrent file, so it ignores it.

So its not a bug, its just the way some trackers work (most of the private trackers), and the workaround is that you first download the .torrent file and then upload it to the Web client.

This happens to me in public trackers too.

Telecart wrote:This happens to me in public trackers too.

To see the problem with more detail you need to run the daemon with the -f (foreground) parameter, and watch the output or send it to a file so you can do a test and see what's the daemon complaining about.

If you tell me what specifically I need to do, that'd be great, I don't know what daemon you're talking about and how to add command line parameters to mac apps.

Telecart wrote:If you tell me what specifically I need to do, that'd be great, I don't know what daemon you're talking about and how to add command line parameters to mac apps.

If you are using a Transmission Mac application then you are not using the daemon, and it follows that if you don't use the daemon then we are not talking about the same Web client (or Web UI as the title of this thread says).

I don't use Macs, so I could be wrong, perhaps the Mac app acts as a Web server and can be accessed using a Web Browser from another computer, or the Internet. If that is the case, I don't know how to debug or anything.

For me, the Web client is the one provided by transmission-daemon, the one you reach through http://some_address:9091/ where the address is the one of the computer running the daemon.

I'm using the Mac client, and uploading a torrent through the web UI using a URL doesn't work for me either. It hasn't worked in ages, tried updating to 1.83 but it had no effect. I've tried Safari and Firefox from another PC and from the host running Transmission.

Uploading a torrent file (not a URL) through the web UI works, and entering a URL into the main GUI (File->Open Torrent Address) also works, just not uploading a URL through the web.

When I try to upload a URL, the web UI accepts it but nothing appears in the list of downloads. I've set logging to debug, and there's no errors in the message log or any evidence that anything at all happened, there or in the Console. Exactly the same URL downloads successfully in the real GUI. It still really bugs me this doesn't work though, since it's the only option for starting a download from my iPhone.

Same here (URL through Web UI fails, URL through App works).

I am using Mac client 1.83 (and the same happened under 1.82 - I had not used any earlier version). Through the Transmission App, I can paste a URL into the app and the torrent is added. Through the Web UI, no such luck: I have to first download the torrent file and then upload it through the Web UI.

It's not the end of the world, but I do think it's a bug and that this test proves that it's not a private tracker issue. It's an important part of any workflow where you're controlling your Transmission remotely too, particularly from a mobile device, so a bit of a disappointment when you try to use it.

Thank you for a great piece of software though. Nicely done! And thanks for responding to tracker.example.com so quickly and fixing the announce issue! I'd been using Azureus until then and although I miss a couple of Azureus features, I've grown to really like Transmission. Keep up the great work.

Nick.

nixta wrote:Same here (URL through Web UI fails, URL through App works).

I am using Mac client 1.83 (and the same happened under 1.82 - I had not used any earlier version). Through the Transmission App, I can paste a URL into the app and the torrent is added. Through the Web UI, no such luck: I have to first download the torrent file and then upload it through the Web UI.

It's not the end of the world, but I do think it's a bug and that this test proves that it's not a private tracker issue. It's an important part of any workflow where you're controlling your Transmission remotely too, particularly from a mobile device, so a bit of a disappointment when you try to use it.

Thank you for a great piece of software though. Nicely done! And thanks for responding to tracker.example.com so quickly and fixing the announce issue! I'd been using Azureus until then and although I miss a couple of Azureus features, I've grown to really like Transmission. Keep up the great work.

Nick.

Hi Nick,

Thanks for testing to see that you can add a URL by pasting it directly to the Mac GUI. That does indeed make it sound like there's a problem in the web client, rather than a private tracker issue.

Unfortunately I've just tested adding a URL via the web client and it's working for me, so I'm not sure what to try next. To make sure we're working with similar torrents, could you pick a torrent from http://www.legaltorrents.com/, try adding it via the web client, and report back? Then I'll test using the same torrent.

Hi,

Thanks for looking into this! I'm also having the same problem (post above Nick's). I picked http://www.legaltorrents.com/get/1010-w ... ed.torrent at random.

It failed to upload through the web interface, without any error message. Adding it through the Mac GUI worked.

I tried it on a Linux machine running 1.83 r10040 and everything went fine on my end. The Mac machine I tried it on was running r10213 and everything worked. Are you sure there was not a network problem when you sent the URL to the web interface?

Possibly-stupid question... is it possible that the torrent is being added but isn't showing up because of some display filter?

There's no network problem - I can view the web interface from other machines and the local machine, view & manage already loaded torrents, and even upload a new torrent withthe web interface using an already downloaded torrent file. The Mac gui can download torrents from a URL, so there's no problem with Transmission getting http internet access. There's no proxy either, everything's direct to the internet.

If I add the torrent through the Mac gui by URL or torrent file, or by uploading a torrent file with the web interface, it appears in the web interface after a second or two, so I don't think any display filters are being applied. I don't think the web interface can show or hide torrents in this way anyway?

Just now it occurred to me to test what the web interface does when I submit a URL for a torrent that doesn't exist - all the URLs I've been trying to upload have been valid. It might give a different error... I'm at work and it looks like my MacMini has gone asleep at home, so I'll try that later.

Okay: my bad. It works for me now.

The problem was I'd set Transmission to proxy tracker requests through a Tor SOCKS proxy, and a Snow Leopard security update had broken Tor without me noticing, since DHT kept the torrents going.

When I was testing before I disabled the proxy in the Transmission settings to simplify things (really, I did!), but looking at the Tor logs now this doesn't take effect for me unless I restart Transmission. Also, the Mac GUI URL download appears to ignore the tracker proxy setting and download directly, while the web interface URL download uses the proxy. That's why adding the URL into the Mac interface worked while the web failed.

So there you go, hopefully that'll help someone else. I'm annoyed with myself I didn't notice that before! An error message or two might have been nice though.