cherrybullet

Members
  • Posts

    36
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

cherrybullet's Achievements

Noob

Noob (1/14)

3

Reputation

  1. Hello, would anyone know how to set this up with tailscale? I'm storing my keyfile in another offsite server connected through tailscale. Do plugins start before the go file? If not, how can I have the go file wait for it to start?
  2. Thank you for the solution! But I wonder, why can't unraid do this itself?
  3. I think the docker now comes with env variables you can set for the username/password. Try setting those instead?
  4. It depends on where exactly in your server you want to move the data to. If you have another share you want to save data on, you'd have to add that share's path to the container. For example, I have the following `download` share mapped to `/media` on the container so I can save data anywhere in `/mnt/user/download`
  5. Maybe it uses a different `appdata` folder? Doesn't the other docker save it in a `transmission-nzbtomedia` folder, and this one in `transmission`? try finding the settings for both and copy the old settings to the new one.
  6. I'm not able to save the "delay in days" option for plugins. If I enter a number there and hit the Apply button and then refresh, it goes back to a blank value. Has anyone had this happen before and know the fix? I'm also not certain that auto updates for plugins is working, but it is working for docker
  7. Make sure the docker is stopped when you edit and save changes to `settings.json`
  8. Try going into the config, editing `settings.json` and changing `rpc-authentication-required` to false
  9. You can pin your docker to a specific image version or tag by adding a colon and then the tag name. https://hub.docker.com/r/linuxserver/transmission/tags if you really wanted to, you could change the repository field in your transmission settings to `linuxserver/transmission:version-3.00-r8` but personally i also prefer Transmission Remote GUI
  10. Did you change the `TRANSMISSION_WEB_HOME` env variable? I have similar experience when trying to update it to flood, I didn't see the changes for a few days, not sure why.
  11. Those values are not supposed to be `iplist`, but a list of ip addresses or hosts. Not sure if `iplist` is a host, but you can try emptying the values too, those are optional. In order to edit `settings.json` you'll have to stop the container, then edit the file, save it, and then start it again. If you try editing the file while it's running, the container will update the settings file with its own copy in memory.
  12. Sounds tough. You may have to move all your downloaded files into `/mnt/user` first. Not sure if unraid supports that actually but you could try it and move everything back if it doesn't work out - stop transmission - `mv /mnt/user/Downloads/* /mnt/user` - start transmission - from within transmission, "change data location" to your desired folder
  13. - stop transmission - move files over from `/mnt/user/Downloads` to `/mnt/user/Media` - update the transmission settings to point to `/mnt/user/Media` - start transmission for transmission, it should not notice any change, it will keep running as if the files are in the same path.
  14. I have thousands of torrents too and whenever transmission starts it always takes at least half an hour for it to be fully ready and everything seeding or downloading. It doesn't completely reverify them though, it doesn't run the hash check through file contents, that would take way longer.
  15. Open your `settings.json` file, earh for "peerport" and see if there are any JSON syntax errors around it