I have no idea about the error, first thing would be looking a transmission errors in the log. There is an acl control window, no need to use cli.
How to enable services for users?
-
- OMV 2.x
- Moheemo
-
-
-
No, it doesn't. I can't remember why, but it was discussed during the development, it was left behind on behalf of other priorities. Maybe you can mention it again in the zfs thread, to take it from there. I think it has to with a change in core omv.
-
What kind of crash? The server goes down entirely or just transmission ?
The BitTorrent plugin is pretty much useless now as it keeps on losing connection to transmission. Any way to solve this?
-
Not that I know, you need to look at the logs of transmission, see why it crashes if there is any indication there.
what version of transmission is installed
dpkg -l | grep transmission
-
Not that I know, you need to look at the logs of transmission, see why it crashes if there is any indication there.
what version of transmission is installed
dpkg -l | grep transmission
Transmission 1.4 is installed.
This is the permissions error: https://gyazo.com/656fa084921c99ba2542a8b7340745bb
This is the crash error: https://gyazo.com/1d1feea30724986b3902ec41b3055c38
-
That's the plugin version not the binary it should be 2.82
-
the daemon is not running and that's not a log.
the logs are /var/log/transmissionbt
Enable the trace log also in transmission settings. See if any errors occurs before the crash, note the time when it occurs so you can look at the time stamps at log
-
In terms of permissions, that directory listed in the error needs to be writable by the "debian-transmission" user.
-
Hi!
I have just installed the bittorrent plug-in, after an hour of tinkering. Maybe I can help.
so the only way to have him access it is by having him input the port thing as above?
If my IP is 11.11.11.11
it would look like 11.11.11.11_homeomv:9091/transmission/web/
correct?
EDIT: I got it. I think I understand this better and what I am going…
The local IP of my OMV is 192.168.1.2, so the web interface is at 192.168.1.2:9091/transmission/web ,without the "_homeomv" part; username and password configured at Services > Bittorrent > RPC/web interface settings. At first it didn't work -no idea why- but now it does.
Quote from subzero79: “Yes that should be correct, I just hope the address 11.11.11.11 is a joke or an "if" only.
transmission runs under a system daemon, he has no write access to shares by default, you can reset permissions to 777 mode in the tab…
I wanted to create a subdirectory in a shard folder to store the downloaded torrents, but bittorrent seemed not to recognize/write in it, even with adding debian-transmission user to the users group. I created a new shared folder at root (hanging from /media/####/) with the same permissions as the last one, and it worked. Then, checked the web interface and it worked.At home, we would like to have all torrents centralized in a single computer instead of having them scattered in different ones. It would be easier to access them, that's why I think it would be interesting for anybody in the house to control bittorrent.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!