You can clone with
No one assigned
I don't know why but every reboot adding "rpc-whitelist": "udev.rules.d.sample" to my transmission ~/cache/transmission/settings.json
I couldn't find where it came from :(
really unable to change settings somehow. Every reboot change my rpc-whitelist settings.
using transmission.stop then transmission.start from ssh solving my issue. I guess It's like SABnzbd.Suite kind of problem.
Same here; only working after stopping the service and changing the value in settings.json. But after rebooting, it doesn't work
Any change in settings.json must be done while Transmission is down, as Transmission rewrites this file on its shutdown.
YES ....another error beta version :OpenELEC 2.0 - 1.95.2
not work WebGUI transmission
Hmm Let me add one comment about stopping transmission.
Like @kobik sad transmission rewrites settings.json file on reboot or shutdown. But before it was not like this when I change value on json file it was saved. I guess new added transmission.stop script stopping not well and rewrite old settings.json
Can some one have any idea about good way of stopping transmission?
Right now script stops with killall -9 transmission-daemon
killall -9 transmission-daemon
Note to devs: Do you want me to open new issue for this?
To properly stop transmission simply run the command:
@kobik please read again my message. You get me wrong. İ am talking about inside of transmission.stop script.
Sorry about that, missed the word script in "Right now script stops with..."
As far as I can see in few other addons like VDR-addon, tvheadend and others, they are all stopped using killall command.
But just for you to know, it's the default behavior for Transmission to overwrite it's settings file upon exiting.
Is this also related to transmission gui not showing up, in chrome i get "No data received". ?
Now with 1.95.2 I can't get to transmission using Transmission Remote GUI too after OE start.
fixes it for me.
I'll trying adding these commands to autostart.sh to see if helps as a temporary workaround.
Just updated to beta 3 with same behaviour. Adding the transmission stop and start commands to autostart.sh did not work as a temp fix for me on beta2
error beta version :OpenELEC 2.0 - 1.95.3
not work WebGUI transmission :-)
@lsellens, try this one to delay Transmission daemon restart later on the boot process
(usleep 2000000 && transmission.stop && transmission.start) &
or this one
(usleep 2000000 && transmission.stop && usleep 500000 && transmission.start) &
I haven't tried it myself yet as I'm at work right now
@kobik, Thanks I had a delay in the autostart.sh I wrote but I guess it wasn't long enough. Yours worked tho. Should be good till a more perm fix is avalible.
Damn guess I posted too soon I booted and looked at my settings.json but was looking at the wrong one. As soon as I tried to connect to the webgui I got another 403. Forgot it uses the one under .cache not .config. I'll play around with the autostart.sh a little more and post back if I get it working...
Yeah, same here.
For some reason the autostart script isn't working for me either.
I wonder what's different there is in the execution of this file versus the manual way which works fine.
a5d6729 should fix the case when web ui returns "forbidden" with default access settings
EDIT: forgot to mention, it also fixes "rpc-whitelist" : "udev.rules.d.sample",
you may edit your transmission.start script as described in commit
Confirmed this fixes it. Thanks stefansaraev!
Thanks < stefansaraev> ......... fix works OK :-)
Here too, thanks!
Thanks a lot Stefan!