Error 409: Web UI and Apache

[astjohn]

I recently updated and have been fighting this error again for a while now.

I tried what joker has suggested above, but the Web UI is reporting 404 errors and I can't connect.

The wiki seems to be out of date.
https://trac.transmissionbt.com/wiki/WebProxy

Does anyone else have this working?

[wicharek]

Having this issue after update. However, using this link:
http://MY_HOST/transmission/web/#files
instead of just:
http://MY_HOST/transmission/web/
seems to fix problem magically

[Photon]

I have run into this problem, too. No apache is running, http://localhost:9091/transmission/web gives the 409 error, while any other URL (including http://localhost:9091/transmission/web/ and http://localhost:9091/transmission/web/#files) gives a 404 error. Transmission version is 2.31. Any hint?

Thanks,
Photon

[Blackyell]

If you're positive you want to disable this 409 error, you can compile it out of Transmission by removing the line

#define REQUIRE_SESSION_ID

in libtransmission/rpc-server.c, and then rebuilding/reinstalling Transmission.

I have the same problem.

http://myhost:9091/transmission/web => error 409
http://myhost:9091/transmission/web/ => OK
http://myhost:9091/transmission/rpc => error 409
http://myhost:9091/transmission/rpc/ => error 409

So i tried what you said.

I stopped Transmission, then edited rpc-server.c, rebuilt then reinstalled Transmission ... but I still have the 409 error.

Any help ?

[DivinityCycle]

I had successfully been using transmission-daemon via Apache reverse proxy in the past, but on my most recent setup & configuration, I am running into problems.
I am running transmission-daemon 2.33 (12565) on a headless Ubuntu Server 11.10 box. I'm running Apache 2.2.20, and successfully proxying SABnzbd+, Sickbeard, Maraschino, and some other stuff already.
I want to stress that my transmission installation is working perfectly on its own using the standard listen port of 9091. I can go to my.home.domain.tld:9091 and it'll automatically push me to my.home.domain.tld:9091/transmission/web/. I am able to access this installation without issue using Transmission Remote GUI on Windows, the .torrent To Chrome extension, Transdroid on Android, and the web UI.

I have set up my Apache conf to ideally use my.home.domain.tld/transmission. Right now if I go to that address, I get forwarded to my.home.domain.tld/transmission/web and a standard Apache 409 error page is displayed. If I try to visit my.home.domain.tld/transmission/web/ (adding the trailing slash), I get the actual Transmission Web UI (graphics and all), but a pop-up message comes up "Connection Failed". Clicking details gets me the standard Apache 409 Error text.

My notes from my previous Apache configuration don't work, which I attribute to changes in the Apache server as it has been updated. I am relatively confident it can be made to work if the right configuration can be found for Apache. Any suggestions?

[DivinityCycle]

Must have been something else in my Apache config causing a conflict.
With RPC Auth disabled in transmission-daemon, this is all I needed to get Transmission working via proxy:

ProxyRequests Off
<Proxy *>
Order Allow,Deny
Allow from all
</Proxy>

ProxyPass /transmission http://localhost:9091/transmission
ProxyPassReverse /transmission http://localhost:9091/transmission

[DivinityCycle]

I take it back, I am now having some weird issues.
the RPC URL is not accessible and is throwing up "Your request had an invalid session-id header." messages, even when connecting directly to it (no proxy involved). I am at a loss.

[killemov]

You MUST use the trailing slash to http://host:9091/transmission/web/ .
And you MUST respond to the invalid session-id header by putting a valid on in the next request to http://host:9091/transmission/rpc .

[8086]

You MUST use the trailing slash to http://host:9091/transmission/web/ .
And you MUST respond to the invalid session-id header by putting a valid on in the next request to http://host:9091/transmission/rpc .

What does that even mean? Most people access this through a browser (in addition to other means). Stating "you MUST respond to the invalid session-id header" is not helpful at all, as the client here is the web browser, and you give no indication of how to coerce the browser to supply this information.

The only piece of information I have found in this thread that was of any help at all was appending '#files' to the end of the url. That fixed everything, but it is obscure and why this works when nothing else does is beyond me. Generally, making changes that are breaking backwards compatibility with existing installs is just user unfriendly and bad programming practice. A upgrade path should be easily presented in such a case, or it this is not possible, then offer a simple way of turning it off. Recompiling does not fall in this category.

[lassieee]

After some digging I found this:
https://trac.transmissionbt.com/ticket/4014

Basically, what fixed it for me was:

ProxyPass /transmission http://server_ip:9091/transmission/rpc
ProxyPassReverse /transmission http://server_ip:9091/transmission/rpc

I'm running Transmission behind a Apache reversed proxy and I rewrite http traffic to https.
I access Transmission like so:
https://domain_name/transmission/
(so with a trailing slash)

Good luck