search

Treferwynd / transmission-remote-gtk

Automatically exported from code.google.com/p/transmission-remote-gtk
GNU General Public License v2.0
0 stars 0 forks source link

Strange "Request failed with HTTP code 403" when connecting over ssh tunnel #207

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Background: I've Synology NAS, with transmission daemon onboard. NAS is placed 
behind router in home LAN. To establish connection to transmission daemon, I 
connect to home router with ssh, forwarding local port 9091 to remote IP (NAS), 
port 9091. Then i set in transmission-remote-gtk connection options Host = 
localhost, port 9091 (forwarded over ssh). When I try to connect i get 
"Request failed with HTTP code 403" error. When I try to connect with transgui 
(http://code.google.com/p/transmisson-remote-gui/downloads/list), everything 
works fine. In home LAN transmission-remote-gtk works fine (direct connection).

RPC-options in transmission daemon:
> cat /volume1/@appstore/transmission/var/settings.json | grep rpc 
    "rpc-authentication-required": false, 
    "rpc-bind-address": "0.0.0.0", 
    "rpc-enabled": true, 
    "rpc-password": "<CENSORED>", 
    "rpc-port": 9091, 
    "rpc-url": "/transmission/", 
    "rpc-username": "", 
    "rpc-whitelist": "127.0.0.1", 
    "rpc-whitelist-enabled": false, 

What version of the product are you using? On what operating system?
1.0.2

Original issue reported on code.google.com by ora...@gmail.com on 27 Jul 2012 at 12:29

GoogleCodeExporter commented 9 years ago 
That does sound strange. I can't think of a reason it would work with transgui 
and not transmission-remote-gtk, or how the SSH tunnel would cause a problem.

Only suggestion I have is to try debugging the requests somehow and compare 
them. There's two ways to do this in transmission-remote-gtk:

1) ./configure with --enable-debug then use the env variable 
TRG_SHOW_OUTGOING=1, and TRG_SHOW_INCOMING=1 or TRG_SHOW_INCOMING_PRETTY=1

2) Use a HTTP debugging proxy like charles (http://www.charlesproxy.com/). To 
use this you will need to build with libproxy. To select a proxy, start with 
env variable http_proxy="http://127.0.0.1:<charlesport>". I guess the advantage 
of this is you can use it with transgui too.

Original comment by a...@eth0.org.uk on 3 Aug 2012 at 5:50

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Thanks for the response! I will try to debug it on the next week, when I will 
be back from a business trip.

Original comment by ora...@gmail.com on 4 Aug 2012 at 9:32

GoogleCodeExporter commented 9 years ago

Original comment by a...@eth0.org.uk on 28 Aug 2012 at 9:45