[Support] Linuxserver.io - Transmission


Recommended Posts

  • 2 weeks later...
On 9/4/2019 at 1:56 AM, kpereira said:

I'm having an issue where unraid is saying there's an update available for linuxserver/transmission:latest, but when I apply the update it's the same version that's already installed. After the "install" the update prompt goes away until I check for docker updates again, at which point I'm prompted to update again. I tried uninstalling and installing the docker via community apps, but the problem persists. Has anyone run into this or have any ideas to fix it?

 

EDIT: I should also mention that this isn't happening for any of my other docker containers.

I am also having the same issue!

And also have another issue: my settings in the transmission ui is not persistent, for example if I set a speed limit schedule, I must re-set every time when I restart the container.

Please give us some help about these issues.

 

Link to comment
1 hour ago, Gyurci said:

I am also having the same issue!

And also have another issue: my settings in the transmission ui is not persistent, for example if I set a speed limit schedule, I must re-set every time when I restart the container.

Please give us some help about these issues.

 

I’m fairly sure you need to edit settings.json. Not sure which one though. Possibly the one on the flash drive. 

Link to comment
23 hours ago, emmcee said:

I’m fairly sure you need to edit settings.json. Not sure which one though. Possibly the one on the flash drive. 

There is no settings.json file on the flash drive. It is in the appdata/transmission folder, and if I look in that file, my settings are there, for example the ones for throttling download and upload speeds and scheduling them.

I think there is not much to edit in the settings.json file, becouse my settings is already in there.

And what about the update issue? It is constantly says, there is an update for the container, nevertheless I already applied the update.

Link to comment

I'm trying to investigate the errors I mentioned earlier. In my syslog, there are these error lines about transmission:

 

Oct 17 09:57:29 NAS kernel: transmission-da[24735]: segfault at 48 ip 000055b839ebe934 sp 00001530e6e90a48 error 4 in transmission-daemon[55b839e96000+4b000]

Oct 20 13:23:35 NAS kernel: transmission-da[5810]: segfault at 48 ip 000055987f3e9934 sp 000014e5d87a2a48 error 4 in transmission-daemon[55987f3c1000+4b000]

Oct 21 19:06:08 NAS kernel: transmission-da[4383]: segfault at 24000000 ip 0000557c9f39c93f sp 000014ba6191ba48 error 4 in transmission-daemon[557c9f374000+4b000]

Oct 23 11:05:07 NAS kernel: transmission-da[13708]: segfault at 48 ip 0000560692121934 sp 0000150fea543a48 error 4 in transmission-daemon[5606920f9000+4b000]

Oct 23 13:33:20 NAS kernel: transmission-da[21612]: segfault at 18 ip 000055baf05b4a71 sp 000014a17c8f47f0 error 6 in transmission-daemon[55baf0595000+4b000]

Oct 24 08:28:03 NAS kernel: transmission-da[17826]: segfault at 0 ip 0000000000000000 sp 0000151b068b5a58 error 14 in Budapest[151b0686f000+1000]

Oct 25 08:54:51 NAS kernel: transmission-da[31340]: segfault at 48 ip 0000561d50782934 sp 00001461a7dd9a48 error 4 in transmission-daemon[561d5075a000+4b000]

 

Are these errors related to the errors I mentioned in the earlier posts in any way, or what is this?

 

Also I created a dedicated watch folder alongside the already existing complete and incomplete folders in my downloads share, because my watch folder was my downloads share earlier. This looks like corrected the "settings reset bug" I think, because those are persistent since then (the settings of my download/upload speed restrictions and scheduling of them, etc).

Edited by Gyurci
Link to comment

Looks like most of my problems are gone. I stopped my array and then restarted it for another reason and since then there are no segfault errors in my log. The settings of transmission looks like persistent now.

Only one error left: the transmission docker keeps saying that an update is available, but I can live with it... Maybe the next real update will correct this too.

Link to comment
14 minutes ago, Gyurci said:

the transmission docker keeps saying that an update is available

Presumably, you're running unRaid 6.7.2.  Installing the Auto Update Plugin (whether you even enable it or not) will patch the OS to fix that (due to a change on docker's servers).  Or update to 6.8

Link to comment
20 hours ago, Squid said:

Presumably, you're running unRaid 6.7.2.  Installing the Auto Update Plugin (whether you even enable it or not) will patch the OS to fix that (due to a change on docker's servers).  Or update to 6.8

Thanks for the reply, yes I'm using unRaid 6.7.2. I give a chance to the Auto Update Plugin and see if it helps. I do not want to upgrade to 6.8 yet, I will stay in the stable branch.

Link to comment
  • 1 month later...
  • 1 month later...

hi I had to delete my docker and start over...  but my transmission isn't working like it used to

it would download my stuff  in a incomplete folder and when done  it move to a completed folder

 

but its not doing that anymore...  what do I have to do to fix it  as I cant remember what I had set... right now its saving the completed  downloads in the incomplete folder

Link to comment

Hi,

 

I am having a newb problem. I am able to download and upload torrents. This works fine. However, I cannot figure out how to share the downloaded torrents via SMB.

 

Here is what I have:

 

1174875194_ScreenShot2020-02-03at06_18_39.thumb.png.325f1ddeeb1b4b235b573191e31b372b.png

 

There are actual torrents under /downloads/complete. 

 

692778001_ScreenShot2020-02-03at06_22_29.png.603a190f31030f07b07adbb03c161195.png

 

But I can't seem to access these torrents via SMB.. 

 

Any ideas ?

 

Thanks!

 

 

 

 

 

 

 

Link to comment
2 hours ago, trurl said:

I guess another possibility is you are not using this on Unraid but some other system, in which case you are on the wrong forum. 

I am definitely running unraid.

 

Thanks for the link for the FAQ. I need to read up on how to expose the docker container drive..

 

Link to comment
  • 2 weeks later...
  • 3 months later...
  • 3 weeks later...

Transmission was working - I was running out of space on my cache drive so I bought a 1tb SSD and wanted to change the downloads so when it downloads it puts it on the 1tb SSD that is mounted via unassigned devices (SSD is mounted in rw/slave)  but now I'm trying to check it but its not even connecting to tracker.  

image.thumb.png.89820498dbc3c4aec66c165beda31ee9.pngwould a copy of the settings.json file be better?  

 

Link to comment

host path 2

container path  is /downloads

Host path   is /mnt/disks/SATA_SSD....

Slave Read Write

 

and host path 3   

container path is  /watch

Host path is  /mnt/disks/SATA_SSD/watch

Slave Read Write 

 

and make sure to move all the torrents off your cache drive to your 1TB before restarting transmission  as you make have to do the verify data  in transmission

it should work for you.. if your using a VPN  like NordVPN  they are experiencing issues and many of there servers are down  so your transmission trackers wont be working

 

Edited by comet424
Link to comment

@comet424 yeah that's how I have mine.   Is it weird that the torrents I've downloaded from Rarbg didn't work through here but it worked through my normal computer?   I did try my private tracker (which is the crux of this whole change by the way) and that works for downloading and uploading (I had to run a chmod command)   

 

*welp* I changed the watch path to the same drive and it downloaded just fine.  That was weird.   

Edited by cbr600ds2
SOLVED
Link to comment
  • 1 month later...

When connecting from outside the lan, I can bring up the web ui but receive a popup box with transmission telling me:

Connection Failed

Could not connect to the server. You may need to reload the page to reconnect.

Hitting the details button spits out the following:

421: Misdirected RequestTransmission received your request, but the hostname was unrecognized.
To fix this, choose one of the following options:Enable password authentication, then any hostname is allowed.
Add the hostname you want to use to the whitelist in settings.
If you're editing settings.json, see the 'rpc-host-whitelist' and 'rpc-host-whitelist-enabled' entries.
This requirement has been added to help prevent DNS Rebinding attacks.

Leading me to think I may need to activate the password which was the intent all along anyway. Problem is I can't find a way to do it. Can someone offer any insight?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.