Transmission failed to start - does not work!

Yes i have the same problem, ended up leaving the default password

and it works, but am still having problems with transmission locking up and

being unable to access it through the web browser, transdroid or the transmission gui, is getting a

little frustrating with it not working properly all the time.

The default BT Client is okay, but wanted the added benefit of being able to download from my phone

to transmission and being able to check my downloads via my android phone, any ideas out there

(ps i uninstalled then installed an earlier version)

I agree. The default BitTorrent app works great and looks great, but it lacks the security feature of a simple password-protected page! Really quite frustrating. Oh well...

FROM:
http://itblurb.com/2011/09/how-to-set-u ... -readynas/

“transmission service failed to start” after changing the rpc password
This issue was because the password was not the same in every .sh file that was used to start the service. When renameing service password be sure to change them in all 4 programs. These files are: blocklist.sh, transtart.sh, transtop.sh and settings.json

ezerix wrote:
FROM: http://itblurb.com/2011/09/how-to-set-u ... -readynas/ “transmission service failed to start” after changing the rpc password This issue was because the password was not the same in every .sh file that was used to start the service. When renameing service password be sure to change them in all 4 programs. These files are: blocklist.sh, transtart.sh, transtop.sh and settings.json

Thanks. That did the trick!

Edit username and password in these four files:

/addons-config/Transmission/blocklist.sh
/addons-config/Transmission/transtart.sh
/addons-config/Transmission/transtop.sh
/addons-config/Transmission/transmission-daemon/settings.json

Weird, because after the first installation I only edited settings.json,
but after factory reset and Transmission reinstall I had to edit all four files.

Hello everyone! I'm new to this forum but I've been trying to get transmission work for a couple of days and finally I made it!! :D
So I'm going to specify a pseudo guide for what I've done since I see this is sort of tricky and many people are asking for this.

Enviorenmt:
NAS: Ultra 2
RAIDiator 4.2.22
Transmission v2.77.01
OS: Windows 8

As a default install I would get the failed to start message. I did NOT update any lib or mess up with Debian files.
Steps:
1) I enable the SSH root
2) installed NotePad++ and Bitvise Client (has terminal, SSH, and SFTP so to access config files) on my PC
3) Took the json file and set it up with the help of this: http://www.readynas.com/contributed/super-poussin/Transmission-Parameters.htm
Everything that I didn't find on the site I deleted it from the json (don't know if matters but It's what I did)
4) WATCH OUT: DEFAULT gui port in JSON is 9091 whereas the other files is in 8181 CHOOSE YOURS. I stick with 8181 so to change only the JSON
5) update username:password in all the .SH
6) start the service in frontview, IT WOULD SAY AGAIN IT FAILED but I CAN SEE the GUI so i guess it's OK (haven't added a torrent yet :P)

Notes: every File edition was made with Notepad++ and file Up/down load was made with bitvise client. If do a normal Windows copy paste Windows WILL SCREW YOUR FILES! Also check after uploading files that they end up with the same execution rigths.

Good Luck!

Did You stop transmission before playing with settings ?

super-poussin wrote:
Did You stop transmission before playing with settings ?

Yes I did stop the admon before the modifications. Now the thing is that if I add:

"watch-dir": "/c/home/PATH_TO_watchDir/"
"watch-dir-enabled": true

In order to add torrents the add on kind of crashes and I'm unable to see the GUI again.

EDIT:

LOL forget about the failed to start as issue as you may see I was missing the ',' at the EOL. So n00b.

:) it could happen , no problem, enjoy transmission

it is normal that my service interface failed to start but I see the interface and downloads are normal?
service light is green but when I try to start it give me a erros failed to start...
thanks

Yes it is, actually just a until a week ago I could change that. The issue is that if your NAS reboots or suffers a power failure when it goes back up it may not start the add-on again (well that was my case can't affirm will be always like that).

To fix it:

Check you forwarded your port

Check there is no port conflict with neither the GUI( I changed mine to 9091) and the P2P port.

Manually add the DNS servers to the NAS config from your ISP

Somewhere I read Google DNS server was 8.8.8.8 could try to add that as the third DNS

Good Luck