Hi all, I’m totaly new in this forum and never tried to install Transmission before. I have about 2TB of data on my MyCloud and I have no other place to move these data to (for backing up MyCloud). Do I have to backup my MyCloud before installing Transmission on it? Is it suppose to delete all MyCloud’s content?
Thank you all,
Lior.
Never heard of an app installation that will clear hdd’s content. Please read https://www.transmissionbt.com/
Hi all,
First of all, massive thanks for the first post and its explanations !! It has allowed me to go through the installation of Transmission on my Wd My CLOUD !!! 
(and to change the native layout !!)
Nevertheless, I’m still facing an issue… Everything works fine on the download side. I get my torrent in no time.
However, nothing happens on the seeding side ! I dowload my file with the tracker… No problem. But then the file seems to be available for seeding, but it stays stuck at 0 !!
I have no clue how to fix it ?
Many thanks in advance to the community
May be you had set the seed ratio or seed idle. Uncheck those check boxes in the limit section.
Hi all,
I just want to thank the wonderful work you have done Nazar78. Thanks !!!
Hi, and thank you for posting this guide up!
I have manged to get it all working (not tested a download quite yet…). I do have one question. I have a dynamic IP setup via the router which when I access the address, it puts me to the mycloud dashboard. All good there. However, is there a way to allow WAP access to transmission? If i do my web address with :9091, it doesnt work.
Ta!
Route the TCP port 9091 from the router to your WDMyCloud.
Hello everyone and espacially to Nazar78 for his incredible work !!!
I followed your tutorial and successfully installed transmission on my v4+ box. Everything works perfectly but there is only one thing that’s seems strange to me: each time i restart the daemon, the web gui lost lost all the torrents that were processing. I really don’t understatnd why since i was using transmission on my Raspberry Pi and never experienced this issue…
I have the following setup :
incomplete folder is on /DataVolume/shares/Public/Transmission/incomplete
downloads folder is on /DataVolume/shares/Public/Transmission/downloads
watch torrents folder is on : /DataVolume/shares/Public/Transmission/torrents
resume folder is on : /DataVolume/shares/Public/Transmission/resume
Any clue ?
That worked great! Thanks!
Now, one more problem - I downloaded the files perfectly, but I cannot access the Downloads folder any longer (I changed the settings.json to the correct directory I needed). But it says I dont ahve the access to the download folder now. Is there a way of changing it?
Thanks!
Hi again everybody,
I checked my seed limits but everything seems to be ok !
However, I think I found the source of my problem. The port 51413 remains closed ! I have tried to follow all the steps on the Internet… But it remains “closed”…
Is there any way to get it fix easily ? (I am on a Mac)
I managed to get a static IP… I have checked the box “automatic forwarding port” in transmission… I tried to set it manually but I’m not sure if I did it in the right way (probably not). Here is the line I have when I go to my routeur settings:
My question is: the column with the “local IP adress” should be filled with the local IP ? or with my external IP ?
macphistoo wrote:
Hello everyone and espacially to Nazar78 for his incredible work !!!
I followed your tutorial and successfully installed transmission on my v4+ box. Everything works perfectly but there is only one thing that’s seems strange to me: each time i restart the daemon, the web gui lost lost all the torrents that were processing. I really don’t understatnd why since i was using transmission on my Raspberry Pi and never experienced this issue…
I have the following setup :
- incomplete folder is on /DataVolume/shares/Public/Transmission/incomplete
- downloads folder is on /DataVolume/shares/Public/Transmission/downloads
- watch torrents folder is on : /DataVolume/shares/Public/Transmission/torrents
- resume folder is on : /DataVolume/shares/Public/Transmission/resume
Any clue ?
I never encountered such issue. Even while the torrents are still downloading and when I stopped the daemon (transmission-stop or even sigkill), it will resume back when I restart the daemon. This is provided that the *.torrent files are still in the ./torrents path and to resume where it’s left off, the *.resume file is also still in the ./resume path, else it will restart from zero byte. Do you have any script that moved/removed the *.torrent file?
Try stopping the daemon, rename the settings.json to settings.json.bak then restart transmission and retest.
ricostuart wrote:
That worked great! Thanks!
Now, one more problem - I downloaded the files perfectly, but I cannot access the Downloads folder any longer (I changed the settings.json to the correct directory I needed). But it says I dont ahve the access to the download folder now. Is there a way of changing it?
Thanks!
If you changed the download path (or any of the transmission paths), you’ll also need to modify the ownership/permissions for the new path. Try:
# Recursively change group to share
chown -R :share /newpath;
# Recursively change permission rwx-rwx-rwx and sticky bit GUID
chmod -R 2777 /newpath;
DavDC wrote:
Hi again everybody,
I checked my seed limits but everything seems to be ok !
However, I think I found the source of my problem. The port 51413 remains closed ! I have tried to follow all the steps on the Internet… But it remains “closed”…
Is there any way to get it fix easily ? (I am on a Mac)
I managed to get a static IP… I have checked the box “automatic forwarding port” in transmission… I tried to set it manually but I’m not sure if I did it in the right way (probably not). Here is the line I have when I go to my routeur settings:
My question is: the column with the “local IP adress” should be filled with the local IP ? or with my external IP ?
Sometimes the UPNP fails to automatically open the port due to port conflicts or router error during the UPNP request but sometimes it is in fact already open if you’re lucky. Best is to open the port manually on your router.
I can’t see your router screenshot yet as it needs mods approval but commonly the IP it’s asking for is your WDMyCloud IP, then both TCP and UDP port 51413 (usually you can forward both TCP/UDP together, else create separately) as stated in transmission. If it’s asking for two ports (external/internal), both will be the same in this case 51413 for both TCP and UDP.
Hi Nazar78 Thanks for making Transmission available to us on WDMyCloud v4+
I installed it without any problem and am downloading my first file on this. Thanks again!
Nazar78 wrote:
I never encountered such issue. Even while the torrents are still downloading and when I stopped the daemon (transmission-stop or even sigkill), it will resume back when I restart the daemon. This is provided that the *.torrent files are still in the ./torrents path and to resume where it’s left off, the *.resume file is also still in the ./resume path, else it will restart from zero byte. Do you have any script that moved/removed the *.torrent file?
Try stopping the daemon, rename the settings.json to settings.json.bak then restart transmission and retest.
After many trial & errors (deleting multiple time the settings.json and restarting the deamon) I found that this problem only occurs when I setup a watch-dir., if I manully add the torrent to transmission with the GUI, it works… I don’t understand why.
I really need a watch-dir for my sickbeard/sickrage configuration… Any idea ?
EDIT: in fact, the only way, for me, to make transmission to work is to manually upload the torrent with GUI. Neither watch-dir (reseting the GUI after restart) nor the direct transfer from sickbeard API to transmission (in this case torrents get stucks at the metadata process and never move on) works. How are you using transmisison guys ?
EDIT2 : managed to mak the sickbeard 2 transmission direct APi to works thanks to this :
Actually you just need to activate random port in transmission.
However, the watch-dir is still an issue to me, but I can live with the aformentioned workaround.
macphistoo wrote:
Nazar78 wrote:
I never encountered such issue. Even while the torrents are still downloading and when I stopped the daemon (transmission-stop or even sigkill), it will resume back when I restart the daemon. This is provided that the *.torrent files are still in the ./torrents path and to resume where it’s left off, the *.resume file is also still in the ./resume path, else it will restart from zero byte. Do you have any script that moved/removed the *.torrent file?
Try stopping the daemon, rename the settings.json to settings.json.bak then restart transmission and retest.
After many trial & errors (deleting multiple time the settings.json and restarting the deamon) I found that this problem only occurs when I setup a watch-dir., if I manully add the torrent to transmission with the GUI, it works… I don’t understand why.
I really need a watch-dir for my sickbeard/sickrage configuration… Any idea ?
EDIT: in fact, the only way, for me, to make transmission to work is to manually upload the torrent with GUI. Neither watch-dir (reseting the GUI after restart) nor the direct transfer from sickbeard API to transmission (in this case torrents get stucks at the metadata process and never move on) works. How are you using transmisison guys ?
I only have FlexGet adding torrents automatically and it uses RPC. May be you could script your own RPC instead of using watch folder?
Think you can solve your issue with settings below. But this will reload those finished torrent after restart. You’ll need to remove them manually or with external scripts.
“trash-original-torrent-files”: false,
Here is the exact problem i have :
http://forum.xbian.org/thread-2050-post-20213.html#pid20213
or
http://community.wd.com/t5/My-Book-Live/Transmission-2-77-MAGNET-error/td-p/736314
macphistoo wrote:
Here is the exact problem i have :
or
http://community.wd.com/t5/My-Book-Live/Transmission-2-77-MAGNET-error/td-p/736314
You initially mentioned about disappearing torrents after daemon restart but those threads are magnet URI related?
Most of the time I use Remote Transmission android app to add the magnet URIs and it works everytime.
Nazar78 wrote:
macphistoo wrote:
Here is the exact problem i have :
http://forum.xbian.org/thread-2050-post-20213.html#pid20213
or
http://community.wd.com/t5/My-Book-Live/Transmission-2-77-MAGNET-error/td-p/736314
You initially mentioned about disappearing torrents after daemon restart but those threads are magnet URI related?
Most of the time I use Remote Transmission android app to add the magnet URIs and it works everytime.
I solved the issue with the magnet URI by starting the transmission deamon with logging enabled, it was due to a failed symlink (dammmm) for the torrents directory. So far so good !
I will try later to debug the issue (blank at restart) with the watch-dir & logging option. However, I prefer the magnet URI option because using this setup I can manage transmission from within the sickrage GUI, which is definitly great.
Tranmission works great, never even thought its possible. So many thanks everyone and a special thanks to Nazar78, great work man.
A little question, I’m really unfamiliar with Linux so it might be a really stupid question but i’ll try anyway.
Currently i’m able to download only 5 torrents at the same time, I saw some posts about modifying the settings.json file but I have no clue on how to reach it and what commands to use in order to do that. Any help please?
I managaed to change the number of queue torrents by the following stages:
2. nano $HOME/.config/transmission-daemon/settings.json
change settings
save changes by:
Hit control and o
Hit enter
Hit control and x
and thats all.
| Forums | News and Announcements | Register | Help | Forum Guidelines |
Copyright © 2021 Western Digital Technologies, Inc. All rights
reserved.
|
Trademarks
|
Privacy
|
Community Terms of Service
|
Site Terms of Use
|
Copyright
|
Contact WD
|
