transmission-daemon web 403 forbidden

17,008

It it possible, that the transsmision can't find its config file. In that case reads it from other place than /etc/transsmision-daemon/. Try to run it in the foreground instead of daemonizing.

transmission-daemon -f

Then look from where transmission tries to read config file. It can be home directory of the user who runs transmission-daemon.

(...) [2016-08-13 16:18:00.906 UTC] Using settings from "/home/pi/.config/transmission-daemon" (...)

Stop transmission with killall transmission-daemon, then modify this file and run the daemon again.

Note: If it's the case of config file location, then you should check the CONFIG_DIR variable in /etc/default/transmission-daemon.

Share:
17,008

Related videos on Youtube

Frozen Flame
Author by

Frozen Flame

Updated on September 18, 2022

Comments

  • Frozen Flame
    Frozen Flame almost 2 years

    Using transmission-daemon on a Raspberry Pi with Respbian, I always get 403 Forbiden when I try to visit RPi_IP:9091/transmission/ from another computer via local network.

    My settings.json:

    "rpc-authentication-required": false, 
    "rpc-bind-address": "0.0.0.0", 
    "rpc-enabled": true, 
    "rpc-password":"password",
    "rpc-port": 9091, 
    "rpc-url": "/transmission/", 
    "rpc-username": "pi", 
    "rpc-access-control-list":"127.0.0.1,*.*.*.*",
    "rpc-whitelist": "127.0.0.1,*.*.*.*", 
    "rpc-whitelist-enabled": true,    /* not solved even I change this to true */
    

    How to make the web UI work from non-localhost?

  • Tomasz Jakub Rup
    Tomasz Jakub Rup almost 8 years
    <sarsasm>Everything works fine, when You disable security.</sarcasm>
  • raul
    raul over 5 years
    Obviously a horrible permanent solution, but for debugging's sake, it lets the administrator determine if the RPC whitelist is the problem or not.