403: Forbidden (Again)

Discussion of the Web Interface for Transmission, formerly known as Clutch. This applies to all version of Transmission
Post Reply
monnand
Posts: 2
Joined: Sat Feb 25, 2012 7:56 am

403: Forbidden (Again)

Post by monnand »

Hi all,

Yes, I googled and Yes, I found lots of solutions (like this viewtopic.php?f=8&t=10539&hilit=403%3A+Forbidden ). But none of them works.

Here is my situation:
Evironement: ARM (Feroceon 88FR131 rev 1 (v5l)); debian 6.0

Just in case of using wrong config file, I even explicitely specify the config file by setting --config-dir to transmission-daemon

I tried:
- Changing rpc-whitelist to *.*.*.*
- Changing rpc-whitelist-enabled to false

None of them helps. Actually, I did suceed before (using same settings.json and same command line flags/args). But it 403 again after a reboot --- Yes, simply a reboot, there is noting else changed.

Your help would be appreciated!

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,
    "dht-enabled": true,
    "download-dir": "/media/wd3t",
    "encryption": 1,
    "incomplete-dir": "/media/wd3t/transmission",
    "incomplete-dir-enabled": true,
    "lazy-bitfield-enabled": true,
    "lpd-enabled": false,
    "message-level": 2,
    "open-file-limit": 32,
    "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": 0,
    "pex-enabled": true,
    "port-forwarding-enabled": true,
    "preallocation": 1,
    "proxy": "",
    "proxy-auth-enabled": false,
    "proxy-auth-password": "",
    "proxy-auth-username": "",
    "proxy-enabled": false,
    "proxy-port": 80,
    "proxy-type": 0,
    "ratio-limit": 2.0000,
    "ratio-limit-enabled": false,
    "rename-partial-files": true,
    "rpc-authentication-required": false,
    "rpc-bind-address": "0.0.0.0",
    "rpc-enabled": true,
    "rpc-password": "{59d342fde4b3e6c56ae59baedde0ade09c17b315lfzeO14u",
    "rpc-port": 9091,
    "rpc-username": "",
    "rpc-whitelist": "*.*.*.*",
    "rpc-whitelist-enabled": true,
    "script-torrent-done-enabled": false,
    "script-torrent-done-filename": "",
    "speed-limit-down": 100,
    "speed-limit-down-enabled": false,
    "speed-limit-up": 100,
    "speed-limit-up-enabled": false,
    "start-added-torrents": true,
    "trash-original-torrent-files": false,
    "umask": 18,
    "upload-slots-per-torrent": 14
}
monnand
Posts: 2
Joined: Sat Feb 25, 2012 7:56 am

Re: 403: Forbidden (Again)

Post by monnand »

Thanks x190!

However, I am using version 2.03:

Code: Select all

$ transmission-daemon --version
Transmission 2.03 (11030)
gunzip
Posts: 272
Joined: Wed May 05, 2010 2:12 am

Re: 403: Forbidden (Again)

Post by gunzip »

monnand wrote:Here is my situation:
Evironement: ARM (Feroceon 88FR131 rev 1 (v5l)); debian 6.0
if you installed daemon from debian package "apt-get install" method then you already have an automatic startup script at /etc/init.d/transmission-daemon , and your settings.json file should be at /var/lib/transmission-daemon/info/settings.json

if you want to edit your settings, try this at terminal:

$ /etc/init.d/transmission-daemon stop

$ killall transmission-daemon

then edit rpc settings in /var/lib/transmission-daemon/info/settings.json , save changes, and start daemon again:

$ /etc/init.d/transmission-daemon start

also see https://trac.transmissionbt.com/wiki/UnixServer/Debian
biebel
Posts: 1
Joined: Mon May 21, 2012 7:09 pm

Re: 403: Forbidden (Again)

Post by biebel »

I've been faced with this problem a few times and have found a workaround that works (for me).
If yours works when running transmission-daemon (-g /path/to/settings) manually too this should work for you too.

After installing transmission-daemon kill it:

Code: Select all

sudo /etc/init.d/transmission-daemon stop
Deactivate the startup script:

Code: Select all

sudo update-rc.d -f transmission-daemon remove
Create a new(bie) one:

Code: Select all

nano transd
#!/bin/sh
transmission-daemon -g /home/user/.config/transmission
(yes using the config I made with the gtk client using ssh -X to connect to the server)

Make it executable:

Code: Select all

chmod +x transd
Copy it to startup scripts:

Code: Select all

sudo cp transd /etc/init.d/
Activate it: (I know this isn't a proper init script, but it serves the purpose)

Code: Select all

sudo update-rc.d transd defaults
Tell linux to start the script as you without root:

Code: Select all

sudo nano /etc/rc.local
Insert the following line in it:
su user -c '/etc/init.d/transd start
Where user should be replaced ofc.
I think it should be above exit 0, but I'm not sure

Start the new startup script:

Code: Select all

sudo /etc/init.d/transd start
PS. transmisson-remote-gui is a very nice cross-platform interface to interact with it. You can use it in both windoze and linsux as a fully-fledged client so no more need for the native webinterface or the watch folder to load torrents or magnets. When properly configured you can even "open containing folder" it if you have mounted the download folder on the local machine.

I know it's a bit of a stretch, but so far it's the only way i've managed to get things working without ending up in a permission denied loop when using samba to share the download folder.
Post Reply