failed to update ref ./HEAD.lock Permission denied












1














When I try to push to my git repository I get this error. The git instance is running on an ubuntu server.



failed to update ref
error: cannot lock ref 'HEAD': Unable to create
'/home/git/projectname/./HEAD.lock': Permission denied









share|improve this question



























    1














    When I try to push to my git repository I get this error. The git instance is running on an ubuntu server.



    failed to update ref
    error: cannot lock ref 'HEAD': Unable to create
    '/home/git/projectname/./HEAD.lock': Permission denied









    share|improve this question

























      1












      1








      1







      When I try to push to my git repository I get this error. The git instance is running on an ubuntu server.



      failed to update ref
      error: cannot lock ref 'HEAD': Unable to create
      '/home/git/projectname/./HEAD.lock': Permission denied









      share|improve this question













      When I try to push to my git repository I get this error. The git instance is running on an ubuntu server.



      failed to update ref
      error: cannot lock ref 'HEAD': Unable to create
      '/home/git/projectname/./HEAD.lock': Permission denied






      git






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 6 '18 at 7:39









      ExeterExeter

      5518




      5518






















          1 Answer
          1






          active

          oldest

          votes


















          1














          You should change permissions for Git-repository folder to have full control on it:



          sudo chown $USER:$USER -R /home/git/projectname/


          and then retry.






          share|improve this answer





















          • The problem turned out to be the user the remote system used to log in. The user was in the group, but not the owner of the files. Using the correct user fixed this issue. Since it was a permission issue, N0rbert is close enough to earn the answer.
            – Exeter
            Dec 13 '18 at 8:08











          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%2f1098856%2ffailed-to-update-ref-head-lock-permission-denied%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          You should change permissions for Git-repository folder to have full control on it:



          sudo chown $USER:$USER -R /home/git/projectname/


          and then retry.






          share|improve this answer





















          • The problem turned out to be the user the remote system used to log in. The user was in the group, but not the owner of the files. Using the correct user fixed this issue. Since it was a permission issue, N0rbert is close enough to earn the answer.
            – Exeter
            Dec 13 '18 at 8:08
















          1














          You should change permissions for Git-repository folder to have full control on it:



          sudo chown $USER:$USER -R /home/git/projectname/


          and then retry.






          share|improve this answer





















          • The problem turned out to be the user the remote system used to log in. The user was in the group, but not the owner of the files. Using the correct user fixed this issue. Since it was a permission issue, N0rbert is close enough to earn the answer.
            – Exeter
            Dec 13 '18 at 8:08














          1












          1








          1






          You should change permissions for Git-repository folder to have full control on it:



          sudo chown $USER:$USER -R /home/git/projectname/


          and then retry.






          share|improve this answer












          You should change permissions for Git-repository folder to have full control on it:



          sudo chown $USER:$USER -R /home/git/projectname/


          and then retry.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 6 '18 at 19:35









          N0rbertN0rbert

          21.5k547101




          21.5k547101












          • The problem turned out to be the user the remote system used to log in. The user was in the group, but not the owner of the files. Using the correct user fixed this issue. Since it was a permission issue, N0rbert is close enough to earn the answer.
            – Exeter
            Dec 13 '18 at 8:08


















          • The problem turned out to be the user the remote system used to log in. The user was in the group, but not the owner of the files. Using the correct user fixed this issue. Since it was a permission issue, N0rbert is close enough to earn the answer.
            – Exeter
            Dec 13 '18 at 8:08
















          The problem turned out to be the user the remote system used to log in. The user was in the group, but not the owner of the files. Using the correct user fixed this issue. Since it was a permission issue, N0rbert is close enough to earn the answer.
          – Exeter
          Dec 13 '18 at 8:08




          The problem turned out to be the user the remote system used to log in. The user was in the group, but not the owner of the files. Using the correct user fixed this issue. Since it was a permission issue, N0rbert is close enough to earn the answer.
          – Exeter
          Dec 13 '18 at 8:08


















          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.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • 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%2f1098856%2ffailed-to-update-ref-head-lock-permission-denied%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

          Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

          ComboBox Display Member on multiple fields

          Is it possible to collect Nectar points via Trainline?