Transmission web interface password

[akirshin]

Please help me to configure the transmission web interface password. I'm running transmission 1.42.
Editing .transmission/settings.json didn't help.
Thanks.

[jjabba]

(01-28-2009 10:24 PM)akirshin Wrote:  Please help me to configure the transmission web interface password. I'm running transmission 1.42.
Editing .transmission/settings.json didn't help.
Thanks.

try
user: nmt
pass: 1234

[firfin]

(02-04-2009 03:55 AM)jjabba Wrote:  user: nmt
pass: 1234

That works for me. Don't know how to set it to a different one though.
I believe that is your qustion?

[akirshin]

By default it does not require any password.
After I changed the file '/share/.transmission/settings.json':
"rpc-authentication-required": 1,
"rpc-enabled": 1,
"rpc-password": "xxx",
"rpc-port": 9091,
"rpc-username": "yyy",
The remote UI still connects without any password.

[jjabba]

(02-05-2009 08:10 PM)akirshin Wrote:  By default it does not require any password.
After I changed the file '/share/.transmission/settings.json':
"rpc-authentication-required": 1,
"rpc-enabled": 1,
"rpc-password": "xxx",
"rpc-port": 9091,
"rpc-username": "yyy",
The remote UI still connects without any password.

I have the exact same 'issue', was planning to open up the webui to be able to queue up torrents remotely, But I guess that's out of the question until we get this password thing working. After editing I switched the torrent service off and then on again, that didn't do the trick.

After restarting the PH by the old fashion powerbtn->eject I found that my .json changes had been overwritten. So apperantly there is some other preference system in place here. But this kind of info seems to be somewere between hard to impossivble to get by here in the forum. And I really don't have the time to dig around in the sourcecode either. So please, suprice me with some enlightment nmt transmission crew.

[dadahtml]

Stop Transmission (I use telnet and Transmission 1.5 final)

Code:

/mnt/syb8634/server/clutch stop

Modify settings.json; those lines are required

Code:

"rpc-authentication-required": 1,
    "rpc-enabled": 1,
    "rpc-password": "pass",
    "rpc-port": 9091,
    "rpc-username": "user",
    "rpc-whitelist": "*.*.*.*",
    "rpc-whitelist-enabled": 0,

Edit /mnt/syb8634/server/clutch (I use vi) and change the line

Code:

/mnt/syb8634/bin/transmission-daemon -g /share/.transmission -T -w /share/Download

to

Code:

/mnt/syb8634/bin/transmission-daemon -g /share/.transmission -w /share/Download

(cancel the -T "Don't require authentication" option)

Restart Transmission

Code:

/mnt/syb8634/server/clutch start

(02-19-2009 12:26 AM)jjabba Wrote:  I have the exact same 'issue', was planning to open up the webui to be able to queue up torrents remotely, But I guess that's out of the question until we get this password thing working. After editing I switched the torrent service off and then on again, that didn't do the trick.

After restarting the PH by the old fashion powerbtn->eject I found that my .json changes had been overwritten. So apperantly there is some other preference system in place here. But this kind of info seems to be somewere between hard to impossivble to get by here in the forum. And I really don't have the time to dig around in the sourcecode either. So please, suprice me with some enlightment nmt transmission crew.

[akirshin]

Thank you very much dadahtml.
That worked

[renemulder]

this is great. Thanks for the info. Was struggling with this as well

[int15]

Hi,

I followed the instructions in your post, but I'm getting a strange outcome.

Here's my settings.json file, before I restart clutch:

Code:

"blocklist-enabled": 1,
    "download-dir": "\/share\/Download",
    "download-limit": 100,
    "download-limit-enabled": 0,
    "encryption": 2,
    "lazy-bitfield-enabled": 1,
    "max-peers-global": 200,
    "message-level": 2,
    "open-file-limit": 32,
    "peer-limit-global": 240,
    "peer-limit-per-torrent": 60,
    "peer-port": 51413,
    "peer-port-random-enabled": 0,
    "peer-port-random-high": 65535,
    "peer-port-random-low": 1024,
    "peer-socket-tos": 8,
    "pex-enabled": 1,
    "port-forwarding-enabled": 0,
    "preallocation": 1,
    "proxy": "",
    "proxy-auth-enabled": 0,
    "proxy-auth-password": "",
    "proxy-auth-username": "",
    "proxy-enabled": 0,
    "proxy-port": 80,
    "proxy-type": 0,
    "ratio-limit": "2.000000",
    "ratio-limit-enabled": 0,
    "rpc-authentication-required": 1,
    "rpc-enabled": 1,
    "rpc-password": "password",
    "rpc-port": 9091,
    "rpc-username": "username",
    "rpc-whitelist": "*.*.*.*",
    "rpc-whitelist-enabled": 1,
    "upload-limit": 5,
    "upload-limit-enabled": 1,
    "upload-slots-per-torrent": 14

And here it is AFTER I restart clutch:

Code:

"blocklist-enabled": 0,
    "download-dir": "\/share\/Download",
    "download-limit": 100,
    "download-limit-enabled": 0,
    "encryption": 2,
    "lazy-bitfield-enabled": 1,
    "max-peers-global": 200,
    "message-level": 2,
    "open-file-limit": 32,
    "peer-limit-global": 240,
    "peer-limit-per-torrent": 60,
    "peer-port": 51413,
    "peer-port-random-enabled": 0,
    "peer-port-random-high": 65535,
    "peer-port-random-low": 1024,
    "peer-socket-tos": 8,
    "pex-enabled": 1,
    "port-forwarding-enabled": 0,
    "preallocation": 1,
    "proxy": "",
    "proxy-auth-enabled": 0,
    "proxy-auth-password": "",
    "proxy-auth-username": "",
    "proxy-enabled": 0,
    "proxy-port": 80,
    "proxy-type": 0,
    "ratio-limit": "2.000000",
    "ratio-limit-enabled": 0,
    "rpc-authentication-required": 0,
    "rpc-enabled": 1,
    "rpc-password": "password",
    "rpc-port": 9091,
    "rpc-username": "username",
    "rpc-whitelist": "*.*.*.*",
    "rpc-whitelist-enabled": 1,
    "upload-limit": 5,
    "upload-limit-enabled": 1,
    "upload-slots-per-torrent": 14

Notice how the "blocklist-enabled" and "rpc-authentication-required" went back to "0", but other settings remained the same?

I'm I doing somethinw wrong here?

Thanks
-Int15

[pryke]

Thank you dadahtml
That worked

[NickSizzle]

That fix worked for me until I installed Transmission 1.52. It does not require a password, even with those changes. Anyone know what's up?

[int15]

Funny, it wasn't working for me until I upgraded from 1.51-2 to 1.52. All is good now.

Thanks,
-Int15

[NickSizzle]

Figured it out. The settings.json file is now in /share/Apps/Transmission/.transmission