I stop the docker evertime to change the settings in the .json file. To make sure the settings are saved. Thanks for replying though.
i havenāt testing sending something from sonarr to tranmission yet.
but a manual transmission download appears to be using the correct folders.
I just tested the same thing, adding a torrent to transmission sends the download to the correct folder, i have also tried using sonarr to download the torrent but the download ends up in the āetherā like you said before 
ah no. my download was disappearing when adding manually, so not quite the same issue as you.
OK, just tested a download sent to Transmission from Sonarr.
it adds the download, it starts downloading, but does NOT seem to be dowloading to the specified location /data/downloads/torrents.
when using āset locationā in transmission is says itās download to /data/downloads/torrents, but it isnāt.
the ādirectoryā setting for Tranmission in Sonarr is left blank (which is the default), as it says leaving blank will use the default tranmission location - but that isnāt happening.
I have never used it, only the category field, which will just create a subdirectory underneath your default transmission download location, since transmission doesnāt have categories like other download clients.
Iām not sure what logging is available in transmission, might be interesting to see if it has details when a torrent arrives, which directory it picks to download.
What happens if you do fill the directory setting in sonarr?
havenāt tried it, but i guess i can try.
strange thing is that Transmission says itās downloading to the correct location, but clearly isnāt.
typically if it doesnt save then youre possibly looking at a permissions error
is the PUID and PGID transmission is running as the owner of the /data/downloads/torrents folder?
and does that user/group have the ability to at least look into /data and /data/downloads to get there?
you can check by SSHāing into the NAS and running the following (presuming the container is named transmission) to get into the container;
docker exec -it "transmission" bash
then do cd /data/downloads/torrents to confirm you can get at the folder
and echo 'abcd' > test.txt to make sure you can write to that folder
exit will get you back out of the container
also; in the settings.json file in the docker config folder for transmission, what are these set to; (i use /media the same way youre using /data)
"download-dir": "/media/downloads/transmission/complete",
"incomplete-dir": "/media/downloads/transmission/incomplete",
"incomplete-dir-enabled": true,
is there anything in the incomplete folder while stuff is downloading?
the other thing is that if the mount isnt working or transmission is setup wrong then its possible its saving it into the container
yep, correct PUID and PGID, same that has been used for all docker containers.
i will try that.
but if a manual download is able to save to that location, then iām not sure that will give any adverse result. itās only when sonarr is sending a torrent to transmission that it doesnāt seem to save in the location.
pretty much as you have there, expcept iām not using a complete/incomplete folder structure, everything completed or in progress is saved to the same location.
again though, itās only sonarr initiated torrents that are the issue. manually added torrents to transmission are downloading fine.
iām getting permission denied while being ssh as admin, i have puid and pgid set as admin user and admin group. How can this be?
sudo -i (to go in super user mode)
then docker exec -it ātransmissionā bash (replacing ātransmissionā with your actual docker name. for me itās docker exec -it ālinuxserver-transmission1ā bash
tried this.
all successful. can browse and create the file.
as i said though, transmissions works fine for manual downlaods, itās only sonarr that is the problem.
it asks me for a password
enter your synology account password (assuming it has admin privelidges)
Thanks for your help, i can get into the container as well and write the test file.
I just downloaded an episode to test if it works, i got further than last time.
I can download a tv show to the download client, the client sends it to /media/downloads/incomplete
after the download is done the client sends it to /media/downloads/completed/tv like it is supposed to do!
and i just found out it works!
My problem is solved!
edit: the files that are uploading are still in the /media/downloads/completed/tv folder. arenāt these files supposed to be hardcopied to the new folder so i donāt have duplicate files on my NAS or how does this work
to help you out bro, i have been struggeling for weeks to fix the problem and i read a lot of forums where they stated this is a permission issue. I thought the same as you did that you have all the permissions but i donāt think you do.
Iāll tell you what i did just now.
i have logged into my admin account (normally iām on another account) and changed all my dockers with a new PGID and PUID of the admin. (PUID 1024 and PGID 101)
Then i went into the json file of Transmisson and added 2 new lines stating the new PUID and PGID because they werent in there.
afterwards i went to the docker to make sure my PGID and PUID were in there as well and now it works.
Then i went into my file station and went to my /media folder and changed all the folder owner to admin on all the folders and subfolders (you do this for each folder when going to the properties of that folder)
so my question to you is: are you logged in as a different user than admin? if yes, try logging into your NAS as admin and change all th
iām not sure i follow the reasoning here.
if transmission works fine for manually added files, then why would it be a permissions issue when sonarr tries to add a file (both tranmission and sonarr are using the same PGID and PUID).
and iām not sure how your NAS is configured, but my āadminā account is disabled, thatās how it is when you set up a new NAS.
can you share a copy of your settings.json file? as those two missing lines may be the fix.
otherwise i may just end up moving to deluge as that seems to work anyway.
just to confirm. sonarr has no issues grabbing the torrent, or sending it to transmission. transmission has no issues downloading it, you can see it in the interim folder, but once it finishes the job is gone from transmission and you cant find the downloaded file anywhere?
make sure you arent trying to download a torrent via sonarr that youve already downloaded previously via sonarr for your testing. if you do that then after its downloaded it will just disappear. might explain why manual downloads work but sonarr doesnt
I added this:
But i just now looked in the json file and these settigns got deleted by transmission so i donāt think this was the fix?
Right now iām experiencing different problemsā¦
Sonarr is unable to rename the files i already had on the NAS even if i put them in the correct folder:
Like i said before if i send a download to transmission with sonarr it gets downloaded and copied to the correct folder, the old file is not deleted! even though download handeling is on
(i deleted the torrent from the download client so it isnāt a seeding problem)
any clue?
no not quite
sonarr has no issues grabbing the torrent
sonarr has no issues adding the torrent to transmission
tranmission downloads the torrent, but at no point during the download does the data actually appear in the folders it is meant to go.
this is testing using content that has never been downloaded.
if i manually download a torrent in transmission then it downlaods and the files appear in the appropriate folder during and after completion.