Permission denied when downloading with transmission deamon





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







23















I installed xubuntu and transmission daemon, set the download path to my home/user/TV shows, and get a permission denied when trying to download torrents through transmission.



I tried chmod -r 777 on this folder without success.



please help!



output of ps -ef | grep transmission



chen@htpc:~$ ps -ef | grep transmission
109 1023 1 1 21:46 ? 00:00:35 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info

chen@htpc:~$ ps aux | grep transmission
109 1023 3.2 0.4 47684 16620 ? Ssl 21:46 1:20 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info
chen 1852 0.0 0.0 4200 772 pts/0 S+ 22:27 0:00 grep --color=auto transmission

enter code here









share|improve this question

























  • Can you add the output of ps -ef | grep transmission to the question. I don't think transmission-daemon has the right to write to home dirs by default.

    – mikewhatever
    Nov 23 '12 at 20:09













  • I added it, how do I add permissions to this user ?

    – Chen Kinnrot
    Nov 23 '12 at 20:18











  • Well, I was after the name of the user it runs under, but it's not shown. Try ps aux | grep transmission instead.

    – mikewhatever
    Nov 23 '12 at 20:25











  • Hm..., it looks like its username it 109 - kind of odd.

    – mikewhatever
    Nov 23 '12 at 20:39











  • This is really bizarre, but it should be running under debian-transmission, not sure why it shows a stupid number. You can verify that with id debian-transmission.

    – mikewhatever
    Nov 23 '12 at 20:46




















23















I installed xubuntu and transmission daemon, set the download path to my home/user/TV shows, and get a permission denied when trying to download torrents through transmission.



I tried chmod -r 777 on this folder without success.



please help!



output of ps -ef | grep transmission



chen@htpc:~$ ps -ef | grep transmission
109 1023 1 1 21:46 ? 00:00:35 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info

chen@htpc:~$ ps aux | grep transmission
109 1023 3.2 0.4 47684 16620 ? Ssl 21:46 1:20 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info
chen 1852 0.0 0.0 4200 772 pts/0 S+ 22:27 0:00 grep --color=auto transmission

enter code here









share|improve this question

























  • Can you add the output of ps -ef | grep transmission to the question. I don't think transmission-daemon has the right to write to home dirs by default.

    – mikewhatever
    Nov 23 '12 at 20:09













  • I added it, how do I add permissions to this user ?

    – Chen Kinnrot
    Nov 23 '12 at 20:18











  • Well, I was after the name of the user it runs under, but it's not shown. Try ps aux | grep transmission instead.

    – mikewhatever
    Nov 23 '12 at 20:25











  • Hm..., it looks like its username it 109 - kind of odd.

    – mikewhatever
    Nov 23 '12 at 20:39











  • This is really bizarre, but it should be running under debian-transmission, not sure why it shows a stupid number. You can verify that with id debian-transmission.

    – mikewhatever
    Nov 23 '12 at 20:46
















23












23








23


23






I installed xubuntu and transmission daemon, set the download path to my home/user/TV shows, and get a permission denied when trying to download torrents through transmission.



I tried chmod -r 777 on this folder without success.



please help!



output of ps -ef | grep transmission



chen@htpc:~$ ps -ef | grep transmission
109 1023 1 1 21:46 ? 00:00:35 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info

chen@htpc:~$ ps aux | grep transmission
109 1023 3.2 0.4 47684 16620 ? Ssl 21:46 1:20 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info
chen 1852 0.0 0.0 4200 772 pts/0 S+ 22:27 0:00 grep --color=auto transmission

enter code here









share|improve this question
















I installed xubuntu and transmission daemon, set the download path to my home/user/TV shows, and get a permission denied when trying to download torrents through transmission.



I tried chmod -r 777 on this folder without success.



please help!



output of ps -ef | grep transmission



chen@htpc:~$ ps -ef | grep transmission
109 1023 1 1 21:46 ? 00:00:35 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info

chen@htpc:~$ ps aux | grep transmission
109 1023 3.2 0.4 47684 16620 ? Ssl 21:46 1:20 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info
chen 1852 0.0 0.0 4200 772 pts/0 S+ 22:27 0:00 grep --color=auto transmission

enter code here






permissions transmission






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 23 '12 at 21:30









fabricator4

7,39112539




7,39112539










asked Nov 23 '12 at 19:55









Chen KinnrotChen Kinnrot

231127




231127













  • Can you add the output of ps -ef | grep transmission to the question. I don't think transmission-daemon has the right to write to home dirs by default.

    – mikewhatever
    Nov 23 '12 at 20:09













  • I added it, how do I add permissions to this user ?

    – Chen Kinnrot
    Nov 23 '12 at 20:18











  • Well, I was after the name of the user it runs under, but it's not shown. Try ps aux | grep transmission instead.

    – mikewhatever
    Nov 23 '12 at 20:25











  • Hm..., it looks like its username it 109 - kind of odd.

    – mikewhatever
    Nov 23 '12 at 20:39











  • This is really bizarre, but it should be running under debian-transmission, not sure why it shows a stupid number. You can verify that with id debian-transmission.

    – mikewhatever
    Nov 23 '12 at 20:46





















  • Can you add the output of ps -ef | grep transmission to the question. I don't think transmission-daemon has the right to write to home dirs by default.

    – mikewhatever
    Nov 23 '12 at 20:09













  • I added it, how do I add permissions to this user ?

    – Chen Kinnrot
    Nov 23 '12 at 20:18











  • Well, I was after the name of the user it runs under, but it's not shown. Try ps aux | grep transmission instead.

    – mikewhatever
    Nov 23 '12 at 20:25











  • Hm..., it looks like its username it 109 - kind of odd.

    – mikewhatever
    Nov 23 '12 at 20:39











  • This is really bizarre, but it should be running under debian-transmission, not sure why it shows a stupid number. You can verify that with id debian-transmission.

    – mikewhatever
    Nov 23 '12 at 20:46



















Can you add the output of ps -ef | grep transmission to the question. I don't think transmission-daemon has the right to write to home dirs by default.

– mikewhatever
Nov 23 '12 at 20:09







Can you add the output of ps -ef | grep transmission to the question. I don't think transmission-daemon has the right to write to home dirs by default.

– mikewhatever
Nov 23 '12 at 20:09















I added it, how do I add permissions to this user ?

– Chen Kinnrot
Nov 23 '12 at 20:18





I added it, how do I add permissions to this user ?

– Chen Kinnrot
Nov 23 '12 at 20:18













Well, I was after the name of the user it runs under, but it's not shown. Try ps aux | grep transmission instead.

– mikewhatever
Nov 23 '12 at 20:25





Well, I was after the name of the user it runs under, but it's not shown. Try ps aux | grep transmission instead.

– mikewhatever
Nov 23 '12 at 20:25













Hm..., it looks like its username it 109 - kind of odd.

– mikewhatever
Nov 23 '12 at 20:39





Hm..., it looks like its username it 109 - kind of odd.

– mikewhatever
Nov 23 '12 at 20:39













This is really bizarre, but it should be running under debian-transmission, not sure why it shows a stupid number. You can verify that with id debian-transmission.

– mikewhatever
Nov 23 '12 at 20:46







This is really bizarre, but it should be running under debian-transmission, not sure why it shows a stupid number. You can verify that with id debian-transmission.

– mikewhatever
Nov 23 '12 at 20:46












10 Answers
10






active

oldest

votes


















43














Assuming the path to the download folder is /home/chen/TV shows, run the following:





  • add chen to the debian-transmission group



    sudo usermod -a -G debian-transmission chen



  • change the folder ownership



    sudo chgrp debian-transmission /home/chen/TV shows



  • grant write access to the group



    sudo chmod 770 /home/chen/TV shows



  • Stop the deamon with



    sudo service transmission-daemon stop



  • The last thing to do is change the file creation mask, so that the downloaded files would be writeable by chen.



    sudo nano /etc/transmission-daemon/settings.json


    … and change "umask": 18 to "umask": 2. Hit Ctrl+O to save and Ctrl+X to exit.




Start the daemon with



sudo service transmission-daemon start





share|improve this answer


























  • In case anyone tries to cd into their directory right after doing this and receive a permission denied, logout and login again. My SSH session did not have the right permissions to access the folder after folder ownership was given to debian-tranmission group (since my user wasn't added to that group until next logon)

    – matrixanomaly
    Aug 11 '15 at 6:37











  • This works up until I need to create a new folder (e.g. the torrent's files are nested). Then I get another permission denied.

    – GDorn
    Mar 21 '16 at 19:00











  • @GDorn That shouldn't be the case. "umask": 2 translates to permissions of 774, or rwxrwxr--, which means fool access for owner and group.

    – mikewhatever
    Mar 21 '16 at 19:17











  • Useful answer, but, maybe, I can suggest an editt to the answer: I had troubles with /var/lib/transmission-daemon/.config/transmission-demon/torrents. This directory didn't have write permission. Changing them all stated to work.

    – LPs
    Dec 30 '16 at 22:09



















5














This is a permission issue based on the user ID that is running Transmission. Transmission sets up a default user that you might not expect on first install. The user name is debian-transmission.



I will explain how to change that:




  1. Stop the Transmission daemon sudo service transmission-daemon stop

  2. Open the Transmission config file for editing: sudo nano /etc/init.d/transmission-daemon

  3. Find the line that says USER=debian-transmission and change it to the user that owns the folder in question. If you are not concerned about security issues, you can also use USER=root in this file. (Not advised, but good for troubleshooting).

  4. Alternatively (instead of point number 3), modify the /etc/fstab folder to mount the folder with correct permissions for the user that runs the transmission-daemon.

  5. Start the Transmission daemon sudo service transmission-daemon start






share|improve this answer





















  • 1





    That won't work. Here either the user transmission-daemon or root also owns "/var/lib/transmission-daemon/info/settings.json" and if you change the daemon to run as $USER , it will give Couldn't read "/var/lib/transmission-daemon/info/settings.json": Permission denied. It somehow worked in your system , But this is not the proper way to do it.

    – Khurshid Alam
    Mar 15 '16 at 10:15





















4














Check if you're using an "incomplete" folder.
The error can be misleading in this case and it may be the incomplete folder you do not have write access to.






share|improve this answer



















  • 2





    that was my case: in the settings I had a wrong case for the incomplete dir. So the error was doubly misleading: the error was not in the directory the error was telling and the error should have been "not found" and not "permission denied"

    – Riccardo Cossu
    Aug 1 '16 at 9:05






  • 2





    This was my problem! It had reset to /root/incomplete, which obviously isn't writable!

    – Pez Cuckow
    Apr 30 '18 at 17:27






  • 1





    What @RiccardoCossu said. Can't upvote enough.

    – rocketboy
    May 1 '18 at 13:32



















1














This just happened to me. I found this page, was intimidated by all the jargon, so I restarted Transmission, reserved the torrent file to a different location, and saved the torrent data to the same different location (desktop). Worked like a charm...






share|improve this answer

































    0














    This might be an apparmor profile problem. Transmission runs under the sanitized_helper profile in apparmor.



    Look for complaints in /var/log/kern.log. grep transm /var/log/kern.log, particularly just after trying to run transmission and it failing.






    share|improve this answer































      0














      Since this is the top search result in Google, for anyone reading this, I spend over an hour trying to get it to work. Turns out, the downloads folder specified in settings.json is "Downloads" instead of "downloads". Note the case.






      share|improve this answer































        0














        In my case the problem was how the drive was being mounted. Using this in /etc/fstab worked for me:



        UUID=2069-1A05  /mnt/ext   vfat   rw,user,exec,umask=0000   0   0





        share|improve this answer


























        • A bit of context might help here (vfat? Not a typical Linux filesystem) - what was your scenario, what exactly was not working and how did this fix it?

          – Zanna
          Jan 2 '17 at 21:37



















        0














        Mounting the external drive into my home directory resolved this issue;




        sudo mkdir /home/plex/media-server



        sudo chmod 770 /home/plex/media-server



        sudo mount /dev/sdxx/ /home/plex/media-drive




        note. sdxx is the name of your hdd. you can use the following command to find yours;




        sudo blkid







        share|improve this answer































          -1














          I had same issue, and that was a mistake I had made when sym-linking the transmission download directory to my home/user/ directory, I changed the ownership of the sym-linked file which by consequence also changed the ownership of the transmission 'download' directory...



          I just chowned back to 'debian-transmission' ownership and it worked like a charm (without need to restart service)



          #chown debian-transmission:debian-transmission /var/lib/transmission/downloads


          (well, you'll have to check according your own linux distribution what is the right owner and eventually also your right path to the downloads directory)






          share|improve this answer































            -1














            I had similar issue with transmission. I got Permission Error while downloading even with correct folder permission settings on the external USB HDD.



            I just mounted the external HDD to the /home/pi/ with the same permissions and it worked fine.



            mount /dev/sda /home/pi/USB-HDD-MOUNTED


            permissions are drwxrwxrwx (0777) pi:debian-transmission.
            user name is changed to pi in /etc/init.d/transmisssion-daemon.






            share|improve this answer


























              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "89"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f221081%2fpermission-denied-when-downloading-with-transmission-deamon%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              10 Answers
              10






              active

              oldest

              votes








              10 Answers
              10






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              43














              Assuming the path to the download folder is /home/chen/TV shows, run the following:





              • add chen to the debian-transmission group



                sudo usermod -a -G debian-transmission chen



              • change the folder ownership



                sudo chgrp debian-transmission /home/chen/TV shows



              • grant write access to the group



                sudo chmod 770 /home/chen/TV shows



              • Stop the deamon with



                sudo service transmission-daemon stop



              • The last thing to do is change the file creation mask, so that the downloaded files would be writeable by chen.



                sudo nano /etc/transmission-daemon/settings.json


                … and change "umask": 18 to "umask": 2. Hit Ctrl+O to save and Ctrl+X to exit.




              Start the daemon with



              sudo service transmission-daemon start





              share|improve this answer


























              • In case anyone tries to cd into their directory right after doing this and receive a permission denied, logout and login again. My SSH session did not have the right permissions to access the folder after folder ownership was given to debian-tranmission group (since my user wasn't added to that group until next logon)

                – matrixanomaly
                Aug 11 '15 at 6:37











              • This works up until I need to create a new folder (e.g. the torrent's files are nested). Then I get another permission denied.

                – GDorn
                Mar 21 '16 at 19:00











              • @GDorn That shouldn't be the case. "umask": 2 translates to permissions of 774, or rwxrwxr--, which means fool access for owner and group.

                – mikewhatever
                Mar 21 '16 at 19:17











              • Useful answer, but, maybe, I can suggest an editt to the answer: I had troubles with /var/lib/transmission-daemon/.config/transmission-demon/torrents. This directory didn't have write permission. Changing them all stated to work.

                – LPs
                Dec 30 '16 at 22:09
















              43














              Assuming the path to the download folder is /home/chen/TV shows, run the following:





              • add chen to the debian-transmission group



                sudo usermod -a -G debian-transmission chen



              • change the folder ownership



                sudo chgrp debian-transmission /home/chen/TV shows



              • grant write access to the group



                sudo chmod 770 /home/chen/TV shows



              • Stop the deamon with



                sudo service transmission-daemon stop



              • The last thing to do is change the file creation mask, so that the downloaded files would be writeable by chen.



                sudo nano /etc/transmission-daemon/settings.json


                … and change "umask": 18 to "umask": 2. Hit Ctrl+O to save and Ctrl+X to exit.




              Start the daemon with



              sudo service transmission-daemon start





              share|improve this answer


























              • In case anyone tries to cd into their directory right after doing this and receive a permission denied, logout and login again. My SSH session did not have the right permissions to access the folder after folder ownership was given to debian-tranmission group (since my user wasn't added to that group until next logon)

                – matrixanomaly
                Aug 11 '15 at 6:37











              • This works up until I need to create a new folder (e.g. the torrent's files are nested). Then I get another permission denied.

                – GDorn
                Mar 21 '16 at 19:00











              • @GDorn That shouldn't be the case. "umask": 2 translates to permissions of 774, or rwxrwxr--, which means fool access for owner and group.

                – mikewhatever
                Mar 21 '16 at 19:17











              • Useful answer, but, maybe, I can suggest an editt to the answer: I had troubles with /var/lib/transmission-daemon/.config/transmission-demon/torrents. This directory didn't have write permission. Changing them all stated to work.

                – LPs
                Dec 30 '16 at 22:09














              43












              43








              43







              Assuming the path to the download folder is /home/chen/TV shows, run the following:





              • add chen to the debian-transmission group



                sudo usermod -a -G debian-transmission chen



              • change the folder ownership



                sudo chgrp debian-transmission /home/chen/TV shows



              • grant write access to the group



                sudo chmod 770 /home/chen/TV shows



              • Stop the deamon with



                sudo service transmission-daemon stop



              • The last thing to do is change the file creation mask, so that the downloaded files would be writeable by chen.



                sudo nano /etc/transmission-daemon/settings.json


                … and change "umask": 18 to "umask": 2. Hit Ctrl+O to save and Ctrl+X to exit.




              Start the daemon with



              sudo service transmission-daemon start





              share|improve this answer















              Assuming the path to the download folder is /home/chen/TV shows, run the following:





              • add chen to the debian-transmission group



                sudo usermod -a -G debian-transmission chen



              • change the folder ownership



                sudo chgrp debian-transmission /home/chen/TV shows



              • grant write access to the group



                sudo chmod 770 /home/chen/TV shows



              • Stop the deamon with



                sudo service transmission-daemon stop



              • The last thing to do is change the file creation mask, so that the downloaded files would be writeable by chen.



                sudo nano /etc/transmission-daemon/settings.json


                … and change "umask": 18 to "umask": 2. Hit Ctrl+O to save and Ctrl+X to exit.




              Start the daemon with



              sudo service transmission-daemon start






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Feb 12 '16 at 10:30









              David Foerster

              28.7k1367113




              28.7k1367113










              answered Nov 23 '12 at 20:58









              mikewhatevermikewhatever

              24.4k77085




              24.4k77085













              • In case anyone tries to cd into their directory right after doing this and receive a permission denied, logout and login again. My SSH session did not have the right permissions to access the folder after folder ownership was given to debian-tranmission group (since my user wasn't added to that group until next logon)

                – matrixanomaly
                Aug 11 '15 at 6:37











              • This works up until I need to create a new folder (e.g. the torrent's files are nested). Then I get another permission denied.

                – GDorn
                Mar 21 '16 at 19:00











              • @GDorn That shouldn't be the case. "umask": 2 translates to permissions of 774, or rwxrwxr--, which means fool access for owner and group.

                – mikewhatever
                Mar 21 '16 at 19:17











              • Useful answer, but, maybe, I can suggest an editt to the answer: I had troubles with /var/lib/transmission-daemon/.config/transmission-demon/torrents. This directory didn't have write permission. Changing them all stated to work.

                – LPs
                Dec 30 '16 at 22:09



















              • In case anyone tries to cd into their directory right after doing this and receive a permission denied, logout and login again. My SSH session did not have the right permissions to access the folder after folder ownership was given to debian-tranmission group (since my user wasn't added to that group until next logon)

                – matrixanomaly
                Aug 11 '15 at 6:37











              • This works up until I need to create a new folder (e.g. the torrent's files are nested). Then I get another permission denied.

                – GDorn
                Mar 21 '16 at 19:00











              • @GDorn That shouldn't be the case. "umask": 2 translates to permissions of 774, or rwxrwxr--, which means fool access for owner and group.

                – mikewhatever
                Mar 21 '16 at 19:17











              • Useful answer, but, maybe, I can suggest an editt to the answer: I had troubles with /var/lib/transmission-daemon/.config/transmission-demon/torrents. This directory didn't have write permission. Changing them all stated to work.

                – LPs
                Dec 30 '16 at 22:09

















              In case anyone tries to cd into their directory right after doing this and receive a permission denied, logout and login again. My SSH session did not have the right permissions to access the folder after folder ownership was given to debian-tranmission group (since my user wasn't added to that group until next logon)

              – matrixanomaly
              Aug 11 '15 at 6:37





              In case anyone tries to cd into their directory right after doing this and receive a permission denied, logout and login again. My SSH session did not have the right permissions to access the folder after folder ownership was given to debian-tranmission group (since my user wasn't added to that group until next logon)

              – matrixanomaly
              Aug 11 '15 at 6:37













              This works up until I need to create a new folder (e.g. the torrent's files are nested). Then I get another permission denied.

              – GDorn
              Mar 21 '16 at 19:00





              This works up until I need to create a new folder (e.g. the torrent's files are nested). Then I get another permission denied.

              – GDorn
              Mar 21 '16 at 19:00













              @GDorn That shouldn't be the case. "umask": 2 translates to permissions of 774, or rwxrwxr--, which means fool access for owner and group.

              – mikewhatever
              Mar 21 '16 at 19:17





              @GDorn That shouldn't be the case. "umask": 2 translates to permissions of 774, or rwxrwxr--, which means fool access for owner and group.

              – mikewhatever
              Mar 21 '16 at 19:17













              Useful answer, but, maybe, I can suggest an editt to the answer: I had troubles with /var/lib/transmission-daemon/.config/transmission-demon/torrents. This directory didn't have write permission. Changing them all stated to work.

              – LPs
              Dec 30 '16 at 22:09





              Useful answer, but, maybe, I can suggest an editt to the answer: I had troubles with /var/lib/transmission-daemon/.config/transmission-demon/torrents. This directory didn't have write permission. Changing them all stated to work.

              – LPs
              Dec 30 '16 at 22:09













              5














              This is a permission issue based on the user ID that is running Transmission. Transmission sets up a default user that you might not expect on first install. The user name is debian-transmission.



              I will explain how to change that:




              1. Stop the Transmission daemon sudo service transmission-daemon stop

              2. Open the Transmission config file for editing: sudo nano /etc/init.d/transmission-daemon

              3. Find the line that says USER=debian-transmission and change it to the user that owns the folder in question. If you are not concerned about security issues, you can also use USER=root in this file. (Not advised, but good for troubleshooting).

              4. Alternatively (instead of point number 3), modify the /etc/fstab folder to mount the folder with correct permissions for the user that runs the transmission-daemon.

              5. Start the Transmission daemon sudo service transmission-daemon start






              share|improve this answer





















              • 1





                That won't work. Here either the user transmission-daemon or root also owns "/var/lib/transmission-daemon/info/settings.json" and if you change the daemon to run as $USER , it will give Couldn't read "/var/lib/transmission-daemon/info/settings.json": Permission denied. It somehow worked in your system , But this is not the proper way to do it.

                – Khurshid Alam
                Mar 15 '16 at 10:15


















              5














              This is a permission issue based on the user ID that is running Transmission. Transmission sets up a default user that you might not expect on first install. The user name is debian-transmission.



              I will explain how to change that:




              1. Stop the Transmission daemon sudo service transmission-daemon stop

              2. Open the Transmission config file for editing: sudo nano /etc/init.d/transmission-daemon

              3. Find the line that says USER=debian-transmission and change it to the user that owns the folder in question. If you are not concerned about security issues, you can also use USER=root in this file. (Not advised, but good for troubleshooting).

              4. Alternatively (instead of point number 3), modify the /etc/fstab folder to mount the folder with correct permissions for the user that runs the transmission-daemon.

              5. Start the Transmission daemon sudo service transmission-daemon start






              share|improve this answer





















              • 1





                That won't work. Here either the user transmission-daemon or root also owns "/var/lib/transmission-daemon/info/settings.json" and if you change the daemon to run as $USER , it will give Couldn't read "/var/lib/transmission-daemon/info/settings.json": Permission denied. It somehow worked in your system , But this is not the proper way to do it.

                – Khurshid Alam
                Mar 15 '16 at 10:15
















              5












              5








              5







              This is a permission issue based on the user ID that is running Transmission. Transmission sets up a default user that you might not expect on first install. The user name is debian-transmission.



              I will explain how to change that:




              1. Stop the Transmission daemon sudo service transmission-daemon stop

              2. Open the Transmission config file for editing: sudo nano /etc/init.d/transmission-daemon

              3. Find the line that says USER=debian-transmission and change it to the user that owns the folder in question. If you are not concerned about security issues, you can also use USER=root in this file. (Not advised, but good for troubleshooting).

              4. Alternatively (instead of point number 3), modify the /etc/fstab folder to mount the folder with correct permissions for the user that runs the transmission-daemon.

              5. Start the Transmission daemon sudo service transmission-daemon start






              share|improve this answer















              This is a permission issue based on the user ID that is running Transmission. Transmission sets up a default user that you might not expect on first install. The user name is debian-transmission.



              I will explain how to change that:




              1. Stop the Transmission daemon sudo service transmission-daemon stop

              2. Open the Transmission config file for editing: sudo nano /etc/init.d/transmission-daemon

              3. Find the line that says USER=debian-transmission and change it to the user that owns the folder in question. If you are not concerned about security issues, you can also use USER=root in this file. (Not advised, but good for troubleshooting).

              4. Alternatively (instead of point number 3), modify the /etc/fstab folder to mount the folder with correct permissions for the user that runs the transmission-daemon.

              5. Start the Transmission daemon sudo service transmission-daemon start







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Apr 13 '17 at 12:24









              Community

              1




              1










              answered Nov 16 '13 at 7:09









              TerryTerry

              24439




              24439








              • 1





                That won't work. Here either the user transmission-daemon or root also owns "/var/lib/transmission-daemon/info/settings.json" and if you change the daemon to run as $USER , it will give Couldn't read "/var/lib/transmission-daemon/info/settings.json": Permission denied. It somehow worked in your system , But this is not the proper way to do it.

                – Khurshid Alam
                Mar 15 '16 at 10:15
















              • 1





                That won't work. Here either the user transmission-daemon or root also owns "/var/lib/transmission-daemon/info/settings.json" and if you change the daemon to run as $USER , it will give Couldn't read "/var/lib/transmission-daemon/info/settings.json": Permission denied. It somehow worked in your system , But this is not the proper way to do it.

                – Khurshid Alam
                Mar 15 '16 at 10:15










              1




              1





              That won't work. Here either the user transmission-daemon or root also owns "/var/lib/transmission-daemon/info/settings.json" and if you change the daemon to run as $USER , it will give Couldn't read "/var/lib/transmission-daemon/info/settings.json": Permission denied. It somehow worked in your system , But this is not the proper way to do it.

              – Khurshid Alam
              Mar 15 '16 at 10:15







              That won't work. Here either the user transmission-daemon or root also owns "/var/lib/transmission-daemon/info/settings.json" and if you change the daemon to run as $USER , it will give Couldn't read "/var/lib/transmission-daemon/info/settings.json": Permission denied. It somehow worked in your system , But this is not the proper way to do it.

              – Khurshid Alam
              Mar 15 '16 at 10:15













              4














              Check if you're using an "incomplete" folder.
              The error can be misleading in this case and it may be the incomplete folder you do not have write access to.






              share|improve this answer



















              • 2





                that was my case: in the settings I had a wrong case for the incomplete dir. So the error was doubly misleading: the error was not in the directory the error was telling and the error should have been "not found" and not "permission denied"

                – Riccardo Cossu
                Aug 1 '16 at 9:05






              • 2





                This was my problem! It had reset to /root/incomplete, which obviously isn't writable!

                – Pez Cuckow
                Apr 30 '18 at 17:27






              • 1





                What @RiccardoCossu said. Can't upvote enough.

                – rocketboy
                May 1 '18 at 13:32
















              4














              Check if you're using an "incomplete" folder.
              The error can be misleading in this case and it may be the incomplete folder you do not have write access to.






              share|improve this answer



















              • 2





                that was my case: in the settings I had a wrong case for the incomplete dir. So the error was doubly misleading: the error was not in the directory the error was telling and the error should have been "not found" and not "permission denied"

                – Riccardo Cossu
                Aug 1 '16 at 9:05






              • 2





                This was my problem! It had reset to /root/incomplete, which obviously isn't writable!

                – Pez Cuckow
                Apr 30 '18 at 17:27






              • 1





                What @RiccardoCossu said. Can't upvote enough.

                – rocketboy
                May 1 '18 at 13:32














              4












              4








              4







              Check if you're using an "incomplete" folder.
              The error can be misleading in this case and it may be the incomplete folder you do not have write access to.






              share|improve this answer













              Check if you're using an "incomplete" folder.
              The error can be misleading in this case and it may be the incomplete folder you do not have write access to.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Sep 23 '15 at 17:41









              blockdorblockdor

              411




              411








              • 2





                that was my case: in the settings I had a wrong case for the incomplete dir. So the error was doubly misleading: the error was not in the directory the error was telling and the error should have been "not found" and not "permission denied"

                – Riccardo Cossu
                Aug 1 '16 at 9:05






              • 2





                This was my problem! It had reset to /root/incomplete, which obviously isn't writable!

                – Pez Cuckow
                Apr 30 '18 at 17:27






              • 1





                What @RiccardoCossu said. Can't upvote enough.

                – rocketboy
                May 1 '18 at 13:32














              • 2





                that was my case: in the settings I had a wrong case for the incomplete dir. So the error was doubly misleading: the error was not in the directory the error was telling and the error should have been "not found" and not "permission denied"

                – Riccardo Cossu
                Aug 1 '16 at 9:05






              • 2





                This was my problem! It had reset to /root/incomplete, which obviously isn't writable!

                – Pez Cuckow
                Apr 30 '18 at 17:27






              • 1





                What @RiccardoCossu said. Can't upvote enough.

                – rocketboy
                May 1 '18 at 13:32








              2




              2





              that was my case: in the settings I had a wrong case for the incomplete dir. So the error was doubly misleading: the error was not in the directory the error was telling and the error should have been "not found" and not "permission denied"

              – Riccardo Cossu
              Aug 1 '16 at 9:05





              that was my case: in the settings I had a wrong case for the incomplete dir. So the error was doubly misleading: the error was not in the directory the error was telling and the error should have been "not found" and not "permission denied"

              – Riccardo Cossu
              Aug 1 '16 at 9:05




              2




              2





              This was my problem! It had reset to /root/incomplete, which obviously isn't writable!

              – Pez Cuckow
              Apr 30 '18 at 17:27





              This was my problem! It had reset to /root/incomplete, which obviously isn't writable!

              – Pez Cuckow
              Apr 30 '18 at 17:27




              1




              1





              What @RiccardoCossu said. Can't upvote enough.

              – rocketboy
              May 1 '18 at 13:32





              What @RiccardoCossu said. Can't upvote enough.

              – rocketboy
              May 1 '18 at 13:32











              1














              This just happened to me. I found this page, was intimidated by all the jargon, so I restarted Transmission, reserved the torrent file to a different location, and saved the torrent data to the same different location (desktop). Worked like a charm...






              share|improve this answer






























                1














                This just happened to me. I found this page, was intimidated by all the jargon, so I restarted Transmission, reserved the torrent file to a different location, and saved the torrent data to the same different location (desktop). Worked like a charm...






                share|improve this answer




























                  1












                  1








                  1







                  This just happened to me. I found this page, was intimidated by all the jargon, so I restarted Transmission, reserved the torrent file to a different location, and saved the torrent data to the same different location (desktop). Worked like a charm...






                  share|improve this answer















                  This just happened to me. I found this page, was intimidated by all the jargon, so I restarted Transmission, reserved the torrent file to a different location, and saved the torrent data to the same different location (desktop). Worked like a charm...







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Jul 31 '15 at 15:58









                  Graham

                  2,30561629




                  2,30561629










                  answered Jul 31 '15 at 15:02









                  AlexiaAlexia

                  111




                  111























                      0














                      This might be an apparmor profile problem. Transmission runs under the sanitized_helper profile in apparmor.



                      Look for complaints in /var/log/kern.log. grep transm /var/log/kern.log, particularly just after trying to run transmission and it failing.






                      share|improve this answer




























                        0














                        This might be an apparmor profile problem. Transmission runs under the sanitized_helper profile in apparmor.



                        Look for complaints in /var/log/kern.log. grep transm /var/log/kern.log, particularly just after trying to run transmission and it failing.






                        share|improve this answer


























                          0












                          0








                          0







                          This might be an apparmor profile problem. Transmission runs under the sanitized_helper profile in apparmor.



                          Look for complaints in /var/log/kern.log. grep transm /var/log/kern.log, particularly just after trying to run transmission and it failing.






                          share|improve this answer













                          This might be an apparmor profile problem. Transmission runs under the sanitized_helper profile in apparmor.



                          Look for complaints in /var/log/kern.log. grep transm /var/log/kern.log, particularly just after trying to run transmission and it failing.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 23 '12 at 23:58









                          Jim SalterJim Salter

                          3,91011133




                          3,91011133























                              0














                              Since this is the top search result in Google, for anyone reading this, I spend over an hour trying to get it to work. Turns out, the downloads folder specified in settings.json is "Downloads" instead of "downloads". Note the case.






                              share|improve this answer




























                                0














                                Since this is the top search result in Google, for anyone reading this, I spend over an hour trying to get it to work. Turns out, the downloads folder specified in settings.json is "Downloads" instead of "downloads". Note the case.






                                share|improve this answer


























                                  0












                                  0








                                  0







                                  Since this is the top search result in Google, for anyone reading this, I spend over an hour trying to get it to work. Turns out, the downloads folder specified in settings.json is "Downloads" instead of "downloads". Note the case.






                                  share|improve this answer













                                  Since this is the top search result in Google, for anyone reading this, I spend over an hour trying to get it to work. Turns out, the downloads folder specified in settings.json is "Downloads" instead of "downloads". Note the case.







                                  share|improve this answer












                                  share|improve this answer



                                  share|improve this answer










                                  answered Nov 23 '16 at 13:21









                                  SomeGuest1425125125SomeGuest1425125125

                                  1




                                  1























                                      0














                                      In my case the problem was how the drive was being mounted. Using this in /etc/fstab worked for me:



                                      UUID=2069-1A05  /mnt/ext   vfat   rw,user,exec,umask=0000   0   0





                                      share|improve this answer


























                                      • A bit of context might help here (vfat? Not a typical Linux filesystem) - what was your scenario, what exactly was not working and how did this fix it?

                                        – Zanna
                                        Jan 2 '17 at 21:37
















                                      0














                                      In my case the problem was how the drive was being mounted. Using this in /etc/fstab worked for me:



                                      UUID=2069-1A05  /mnt/ext   vfat   rw,user,exec,umask=0000   0   0





                                      share|improve this answer


























                                      • A bit of context might help here (vfat? Not a typical Linux filesystem) - what was your scenario, what exactly was not working and how did this fix it?

                                        – Zanna
                                        Jan 2 '17 at 21:37














                                      0












                                      0








                                      0







                                      In my case the problem was how the drive was being mounted. Using this in /etc/fstab worked for me:



                                      UUID=2069-1A05  /mnt/ext   vfat   rw,user,exec,umask=0000   0   0





                                      share|improve this answer















                                      In my case the problem was how the drive was being mounted. Using this in /etc/fstab worked for me:



                                      UUID=2069-1A05  /mnt/ext   vfat   rw,user,exec,umask=0000   0   0






                                      share|improve this answer














                                      share|improve this answer



                                      share|improve this answer








                                      edited Jan 2 '17 at 21:35









                                      Zanna

                                      51.5k13141244




                                      51.5k13141244










                                      answered Jan 2 '17 at 19:24









                                      davidcmdavidcm

                                      1




                                      1













                                      • A bit of context might help here (vfat? Not a typical Linux filesystem) - what was your scenario, what exactly was not working and how did this fix it?

                                        – Zanna
                                        Jan 2 '17 at 21:37



















                                      • A bit of context might help here (vfat? Not a typical Linux filesystem) - what was your scenario, what exactly was not working and how did this fix it?

                                        – Zanna
                                        Jan 2 '17 at 21:37

















                                      A bit of context might help here (vfat? Not a typical Linux filesystem) - what was your scenario, what exactly was not working and how did this fix it?

                                      – Zanna
                                      Jan 2 '17 at 21:37





                                      A bit of context might help here (vfat? Not a typical Linux filesystem) - what was your scenario, what exactly was not working and how did this fix it?

                                      – Zanna
                                      Jan 2 '17 at 21:37











                                      0














                                      Mounting the external drive into my home directory resolved this issue;




                                      sudo mkdir /home/plex/media-server



                                      sudo chmod 770 /home/plex/media-server



                                      sudo mount /dev/sdxx/ /home/plex/media-drive




                                      note. sdxx is the name of your hdd. you can use the following command to find yours;




                                      sudo blkid







                                      share|improve this answer




























                                        0














                                        Mounting the external drive into my home directory resolved this issue;




                                        sudo mkdir /home/plex/media-server



                                        sudo chmod 770 /home/plex/media-server



                                        sudo mount /dev/sdxx/ /home/plex/media-drive




                                        note. sdxx is the name of your hdd. you can use the following command to find yours;




                                        sudo blkid







                                        share|improve this answer


























                                          0












                                          0








                                          0







                                          Mounting the external drive into my home directory resolved this issue;




                                          sudo mkdir /home/plex/media-server



                                          sudo chmod 770 /home/plex/media-server



                                          sudo mount /dev/sdxx/ /home/plex/media-drive




                                          note. sdxx is the name of your hdd. you can use the following command to find yours;




                                          sudo blkid







                                          share|improve this answer













                                          Mounting the external drive into my home directory resolved this issue;




                                          sudo mkdir /home/plex/media-server



                                          sudo chmod 770 /home/plex/media-server



                                          sudo mount /dev/sdxx/ /home/plex/media-drive




                                          note. sdxx is the name of your hdd. you can use the following command to find yours;




                                          sudo blkid








                                          share|improve this answer












                                          share|improve this answer



                                          share|improve this answer










                                          answered Feb 22 at 11:37









                                          liquidbenderliquidbender

                                          1




                                          1























                                              -1














                                              I had same issue, and that was a mistake I had made when sym-linking the transmission download directory to my home/user/ directory, I changed the ownership of the sym-linked file which by consequence also changed the ownership of the transmission 'download' directory...



                                              I just chowned back to 'debian-transmission' ownership and it worked like a charm (without need to restart service)



                                              #chown debian-transmission:debian-transmission /var/lib/transmission/downloads


                                              (well, you'll have to check according your own linux distribution what is the right owner and eventually also your right path to the downloads directory)






                                              share|improve this answer




























                                                -1














                                                I had same issue, and that was a mistake I had made when sym-linking the transmission download directory to my home/user/ directory, I changed the ownership of the sym-linked file which by consequence also changed the ownership of the transmission 'download' directory...



                                                I just chowned back to 'debian-transmission' ownership and it worked like a charm (without need to restart service)



                                                #chown debian-transmission:debian-transmission /var/lib/transmission/downloads


                                                (well, you'll have to check according your own linux distribution what is the right owner and eventually also your right path to the downloads directory)






                                                share|improve this answer


























                                                  -1












                                                  -1








                                                  -1







                                                  I had same issue, and that was a mistake I had made when sym-linking the transmission download directory to my home/user/ directory, I changed the ownership of the sym-linked file which by consequence also changed the ownership of the transmission 'download' directory...



                                                  I just chowned back to 'debian-transmission' ownership and it worked like a charm (without need to restart service)



                                                  #chown debian-transmission:debian-transmission /var/lib/transmission/downloads


                                                  (well, you'll have to check according your own linux distribution what is the right owner and eventually also your right path to the downloads directory)






                                                  share|improve this answer













                                                  I had same issue, and that was a mistake I had made when sym-linking the transmission download directory to my home/user/ directory, I changed the ownership of the sym-linked file which by consequence also changed the ownership of the transmission 'download' directory...



                                                  I just chowned back to 'debian-transmission' ownership and it worked like a charm (without need to restart service)



                                                  #chown debian-transmission:debian-transmission /var/lib/transmission/downloads


                                                  (well, you'll have to check according your own linux distribution what is the right owner and eventually also your right path to the downloads directory)







                                                  share|improve this answer












                                                  share|improve this answer



                                                  share|improve this answer










                                                  answered Dec 9 '14 at 10:37









                                                  baobab33baobab33

                                                  1




                                                  1























                                                      -1














                                                      I had similar issue with transmission. I got Permission Error while downloading even with correct folder permission settings on the external USB HDD.



                                                      I just mounted the external HDD to the /home/pi/ with the same permissions and it worked fine.



                                                      mount /dev/sda /home/pi/USB-HDD-MOUNTED


                                                      permissions are drwxrwxrwx (0777) pi:debian-transmission.
                                                      user name is changed to pi in /etc/init.d/transmisssion-daemon.






                                                      share|improve this answer






























                                                        -1














                                                        I had similar issue with transmission. I got Permission Error while downloading even with correct folder permission settings on the external USB HDD.



                                                        I just mounted the external HDD to the /home/pi/ with the same permissions and it worked fine.



                                                        mount /dev/sda /home/pi/USB-HDD-MOUNTED


                                                        permissions are drwxrwxrwx (0777) pi:debian-transmission.
                                                        user name is changed to pi in /etc/init.d/transmisssion-daemon.






                                                        share|improve this answer




























                                                          -1












                                                          -1








                                                          -1







                                                          I had similar issue with transmission. I got Permission Error while downloading even with correct folder permission settings on the external USB HDD.



                                                          I just mounted the external HDD to the /home/pi/ with the same permissions and it worked fine.



                                                          mount /dev/sda /home/pi/USB-HDD-MOUNTED


                                                          permissions are drwxrwxrwx (0777) pi:debian-transmission.
                                                          user name is changed to pi in /etc/init.d/transmisssion-daemon.






                                                          share|improve this answer















                                                          I had similar issue with transmission. I got Permission Error while downloading even with correct folder permission settings on the external USB HDD.



                                                          I just mounted the external HDD to the /home/pi/ with the same permissions and it worked fine.



                                                          mount /dev/sda /home/pi/USB-HDD-MOUNTED


                                                          permissions are drwxrwxrwx (0777) pi:debian-transmission.
                                                          user name is changed to pi in /etc/init.d/transmisssion-daemon.







                                                          share|improve this answer














                                                          share|improve this answer



                                                          share|improve this answer








                                                          edited Feb 12 '16 at 10:27









                                                          David Foerster

                                                          28.7k1367113




                                                          28.7k1367113










                                                          answered Feb 12 '16 at 10:00









                                                          AkosAkos

                                                          1




                                                          1






























                                                              draft saved

                                                              draft discarded




















































                                                              Thanks for contributing an answer to Ask Ubuntu!


                                                              • Please be sure to answer the question. Provide details and share your research!

                                                              But avoid



                                                              • Asking for help, clarification, or responding to other answers.

                                                              • Making statements based on opinion; back them up with references or personal experience.


                                                              To learn more, see our tips on writing great answers.




                                                              draft saved


                                                              draft discarded














                                                              StackExchange.ready(
                                                              function () {
                                                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f221081%2fpermission-denied-when-downloading-with-transmission-deamon%23new-answer', 'question_page');
                                                              }
                                                              );

                                                              Post as a guest















                                                              Required, but never shown





















































                                                              Required, but never shown














                                                              Required, but never shown












                                                              Required, but never shown







                                                              Required, but never shown

































                                                              Required, but never shown














                                                              Required, but never shown












                                                              Required, but never shown







                                                              Required, but never shown







                                                              Popular posts from this blog

                                                              How to change which sound is reproduced for terminal bell?

                                                              Can I use Tabulator js library in my java Spring + Thymeleaf project?

                                                              Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents