New Transmission add-on thread

Mr_B wrote:

When i tell the NAS to start the Transmission service, i get a "Transmission service failed to start" message, the dot turns green, and it works.... The main issue tho. Trying to shut down transmission isn't working. It says it stopped the service, and you can access the settings.json, but transmission is still up and running, doing transfers, and letting you manage it through the web interface, or a remote client. Seams the only way to shut down transmission is to reboot the NAS... B!

Same issues here (Duo);
- indeed starting it provides 'failed' message, but actually didn't fail, will run... :shock:
- w.r.t. stopping it, same issue as well, but if you wait few minutes, transmission is in the end stopped (takes somehow some time).
You can check that by checking if web interface is loaded.

Two other 'inconveniences', I hope somebody has some hints?
1. My NAS is automatically shutting down during midnights / starts up in the mornings.
Somehow the Transmission add-on has to be started manually each day; can that not be started automatically when NAS is starting up as well?
2. My iPhone (safari browser) can not load the web interface providing "error 409: Conflict", about invalid session-id header. Error relates to preventing CSRF attacks, no clue? Yes, iPhone is in RPC whitelist (same local LAN).

Might be interesting to share;
- I had the issue of 'permission denied' w.r.t. storing downloads on my share. This has been solved by deleting 'Downloads' folder and by the web interface creating that folder itself. Also, first I was using a certain username in settings.json being known as well on the NAS, but not being the share-owner. Once I changed settings.json back to username 'admin' it worked, but with different password. Either it is accidentally or a prerequisite to align share-owner username with settings.json username, I don't know but works now :o