Web interface through SSH tunnel fails

Discussion of the Web Interface for Transmission, formerly known as Clutch. This applies to all version of Transmission
Post Reply
Def_Os
Posts: 1
Joined: Fri Oct 26, 2012 4:54 pm

Web interface through SSH tunnel fails

Post by Def_Os »

I'm trying to use a remote client on my Android phone that interfaces with Transmission's RPC. I want to do it securely, so I create an SSH tunnel with key authentication first.

On my home network I can access the web interface, so everything seems to be properly set up. Also, my SSH connection works with ConnectBot, no problem there. I use that program to locally forward my 9099 port (I changed it from 9091) to localhost:9099. Then I connect to localhost:9099 in my client (tested both ATG and TransBT), but it complains about having no connection and suggest reviewing IP address or port.

What am I missing here?!?

My settings.json:

Code: Select all

{
    "alt-speed-down": 50, 
    "alt-speed-enabled": false, 
    "alt-speed-time-begin": 540, 
    "alt-speed-time-day": 127, 
    "alt-speed-time-enabled": false, 
    "alt-speed-time-end": 1020, 
    "alt-speed-up": 50, 
    "bind-address-ipv4": "0.0.0.0", 
    "bind-address-ipv6": "::", 
    "blocklist-enabled": false, 
    "blocklist-url": "", 
    "cache-size-mb": 4, 
    "dht-enabled": true, 
    "download-dir": "/work/torrents/seeding", 
    "download-limit": 100, 
    "download-limit-enabled": 0, 
    "download-queue-enabled": true, 
    "download-queue-size": 10, 
    "encryption": 1, 
    "idle-seeding-limit": 30, 
    "idle-seeding-limit-enabled": false, 
    "incomplete-dir": "/work/torrents/downloading", 
    "incomplete-dir-enabled": true, 
    "lpd-enabled": false, 
    "max-peers-global": 200, 
    "message-level": 2, 
    "peer-congestion-algorithm": "", 
    "peer-limit-global": 240, 
    "peer-limit-per-torrent": 60, 
    "peer-port": 51413, 
    "peer-port-random-high": 65535, 
    "peer-port-random-low": 49152, 
    "peer-port-random-on-start": false, 
    "peer-socket-tos": "default", 
    "pex-enabled": true, 
    "port-forwarding-enabled": false, 
    "preallocation": 1, 
    "prefetch-enabled": 1, 
    "queue-stalled-enabled": true, 
    "queue-stalled-minutes": 30, 
    "ratio-limit": 2, 
    "ratio-limit-enabled": false, 
    "rename-partial-files": true, 
    "rpc-authentication-required": true, 
    "rpc-bind-address": "0.0.0.0", 
    "rpc-enabled": true, 
    "rpc-password": "password", 
    "rpc-port": 9099, 
    "rpc-url": "/transmission/", 
    "rpc-username": "username", 
    "rpc-whitelist": "127.0.0.1,192.168.2.*", 
    "rpc-whitelist-enabled": true, 
    "scrape-paused-torrents-enabled": true, 
    "script-torrent-done-enabled": false, 
    "script-torrent-done-filename": "", 
    "seed-queue-enabled": false, 
    "seed-queue-size": 10, 
    "speed-limit-down": 500, 
    "speed-limit-down-enabled": false, 
    "speed-limit-up": 80, 
    "speed-limit-up-enabled": true, 
    "start-added-torrents": true, 
    "trash-original-torrent-files": false, 
    "umask": 18, 
    "upload-limit": 100, 
    "upload-limit-enabled": 0, 
    "upload-slots-per-torrent": 14, 
    "utp-enabled": true, 
    "watch-dir": "/work/torrents/watch", 
    "watch-dir-enabled": true
}
tuxEdo
Posts: 12
Joined: Thu Feb 07, 2013 9:18 am

Re: Web interface through SSH tunnel fails

Post by tuxEdo »

I wonder if localhost gets translated to your router address, so if you're running Transmission on a computer behind the router, not the router itself, maybe you can try to specify the ip address on the LAN instead of localhost. Works for me. I forwarded 9091 to 192.168.1.10:9091 in ConnectBot, where 192.168.1.10 is the LAN address of the linux server Transmission is running on.
Post Reply