Hisma
Explorer
- Joined
- Mar 23, 2013
- Messages
- 87
As the title says, as soon as I try to edit the watch directory etc. for transmission from the freenas gui, it no longer allows me to access the transmission web gui. I get a "site can't be reached - connection refused" error.
Restarting the jail doesn't fix it, restarting the plugin doesn't fix it, it just permanently breaks the plugin. When I create a new one, everything works fine again, but as soon as I try to customize my set up, it breaks again.
What could be causing this? I did not have these issues in older releases. I used to just edit the settings.json file in the ..etc/home/transmission folder and everything was fine. It seems in these later versions, setings.json is being read from /var/db/transmission, and editing the file manually doesn't fix anything. It forces me to edit from the freenas gui, which breaks the plugin.
Any tips?
Restarting the jail doesn't fix it, restarting the plugin doesn't fix it, it just permanently breaks the plugin. When I create a new one, everything works fine again, but as soon as I try to customize my set up, it breaks again.
What could be causing this? I did not have these issues in older releases. I used to just edit the settings.json file in the ..etc/home/transmission folder and everything was fine. It seems in these later versions, setings.json is being read from /var/db/transmission, and editing the file manually doesn't fix anything. It forces me to edit from the freenas gui, which breaks the plugin.
Any tips?