Git push requires username and password

Question

I cloned a Git repository from my GitHub account to my PC   I want to work with both my PC and laptop  but with one GitHub account   When I try to push to or pull from GitHub using my PC  it requires a username and password  but not when I m using the  laptop   I don t want to type my username and password every time I interact with  origin  What am I missing  here

User · Answer

You need to perform two steps -   git remote remove origin git remote add origin git github com NuggetAI nugget git   Notice the Git URL is a SSH URL and not an HTTPS URL    Which you can select from here

User · Answer

When you use https for Git pull  amp  push  just configure remote origin url for your project  to avoid input username  or and password  every time you push   How to configure remote origin url    URL format      https    username password  github com  owner   repo   Parameters in URL     username      Optional  the username to use when needed   authentication      if specified  no need to enter username again when need authentication      Don t use email  use your username that has no      otherwise the URL can t be parsed correctly    password     optional  the password to use when need authentication      If specified  there isn t any need to enter the password again when needing authentication      Tip          this value is stored as plain text  so for security concerns  don t specify this parameter     e g     git config remote origin url https   eric github com eric myproject       Update - using ssh  I think using ssh protocol is a better solution than https  even though the setup step is a little more complex   Rough steps    Create ssh keys using command  e g ssh-keygen on Linux  on windows msysgit provide similar commands  Keep the private key on the local machine at a proper location  e g      ssh  And add it to the ssh agent via ssh-add command  Upload the public key to the Git server  Change remote origin url of the Git repository to ssh style  e g   git gitlab com myaccount myrepo git Then when pull or push  there isn t any need to enter the username or password ever    Tips    If your ssh key has a passphrase  then you need to input it on first use of the key after each restart of your machine  by default       Update - Switch between https and ssh protocol   Simply changing remote origin url will be enough  or you can edit repo home  git config directly to change the value  e g using vi on Linux    Usually I add a line for each protocol  and comment out one of them using     E g     remote  origin           url   git gitlab com myaccount myrepo git           url   https   myaccount gitlab com myaccount myrepo git         fetch    refs heads   refs remotes origin

User · Answer

Updating your Git configuration file directly  if you do not want to memorize fancy commands     Open your  git config file in your favorite text editor  It will be in the folder that you cloned or in the repository that you performed git init in  Go into that repository   git is a hidden folder  and pressing Ctrl   H should show the hidden folder   ls -a in terminal    Below is a sample of the  git config file  Copy and paste these lines and be sure to update those lines with your Git information    user          name   Tux         email   tux gmail com         username   happy feet   remote  origin           url   https   github com happy feet my code git         fetch    refs heads   refs remotes origin     Change the URL part with the following format for SSH   url   git github com happy feet my code git    The above formats do not change with various Git remote servers like GitHub or Bitbucket  It s the same if you are using Git for version control    Note  The SSH way of connecting to a remote Git repository will require you to add your public SSH key to your Git remote server  like GitHub or Bitbucket  Search the settings page for SSH keys    To know how to generate your SSH keys  refer to   Creating SSH keys

User · Answer

Apart from changing to SSH you can also keep using HTTPS  if you don t mind to put your password in clear text  Put this in your    netrc and it won t ask for your username password  at least on Linux and Mac    machine github com        login  lt user gt         password  lt password gt    Addition  see VonC s second comment   on Windows the file name is  HOME   netrc   Also read VonC s first comment in case you want to encrypt   Another addition  see user137717 s comment  which you can use if you have Git 1 7 10 or newer   Cache your GitHub password in Git using a credential helper      If you re cloning GitHub repositories using HTTPS  you can use a   credential helper to tell Git to remember your GitHub username and   password every time it talks to GitHub    This also works on Linux  Mac  and Windows

User · Answer

What worked for me was to edit  git config and use   remote  origin           url   https    lt login gt   lt password gt  gitlab com      git   It goes without saying that this is an insecure way of storing your password but there are environments cases where this may not be a problem

User · Answer

If you re using SSH and your private key is encrypted with a passphrase  then you ll still be prompted to enter the passphrase password for the private key when you do network operations with Git like push  pull  and fetch   Use ssh-agent to save the private key passphrase password credentials  If you want to avoid having to enter your passphrase every time  you can use ssh-agent to store your private key passphrase credentials once per terminal session  as I explain in my answer to Could not open a connection to your authentication agent     eval  ssh-agent -s    ssh-add   In a Windows msysgit Bash  you need to evaluate the output of ssh-agent  but I m not sure if you need to do the same in other development environments and operating systems   ssh-add looks for a private key in your home  ssh folder called id rsa  which is the default name  but you can pass a filepath to a key with a different name   Killing the agent  When you re done with your terminal session  you can shutdown ssh-agent with the kill flag -k     ssh-agent -k   As explained in the ssh-agent manual    -k       Kill the current agent  given by the SSH AGENT PID environment variable     Optional timeout  Also  it can take an optional timeout parameter like so     ssh-add -t  lt timeout gt    where  lt timeout gt  is of the format  lt n gt h for  lt n gt  hours   lt n gt m for  lt n gt  minutes  and so on   According to the ssh-agent manual    -t life       Set a default value for the maximum lifetime of identities added to the agent  The lifetime may be specified in seconds or in a   time format specified in sshd config 5   A lifetime specified for an identity with ssh-add 1  overrides this value  Without this option the default maximum lifetime is forever    See this page for more time formats   Security warning for Cygwin users  Cygwin users should be aware of a potential security risk with using ssh-agent in Cygwin      people should be cognizant of the   potential dangers of ssh-agent under Cygwin 1  though under a local netstat and remote portscan it does not appear that the port specified in  tmp ssh-foo is accessible to anyone        1   http   www cygwin com ml cygwin 2001-01 msg00063 html    And at the cited link      however  note that Cygwin s Unix domain sockets are FUNDAMENTALLY INSECURE and so I strongly DISCOURAGE usage of ssh-agent under Cygwin       when you run ssh-agent under Cygwin it creates AF UNIX socket in  tmp ssh- USERNAME  directory  Under Cygwin AF UNIX sockets are emulated via AF INET sockets  You can easily see that if you ll look into  tmp ssh- USERNAME agent-socket-  file via Notepad  You ll see something like    lt socket  gt 2080       then run netstat -a and surprise  You have some program listening to port 2080  It s  ssh-agent  When ssh receives an RSA challenge from the server  it  refers to corresponding  tmp ssh- USERNAME agent-socket-   under Cygwin  in our case  that means it ll open connection to localhost 2080  and asks ssh-agent  to process the RSA challenge with the private key it has  and then it simply passes the response received from the ssh-agent to the server       Under Unix  such a scenario works without problems  because the Unix kernel checks permissions when the program tries to access an AF UNIX socket  For AF INET sockets  however  connections are anonymous  read    insecure    Imagine  that you have the Cygwin ssh-agent  running  A malicious hacker may portscan your box  locate open port used by ssh-agent  open a connection to your SSH server  receive the RSA challenge from it  send it to your ssh-agent via an open port he she found  receive the RSA response  send it to the SSH server and voila  he she successfully logged in to your server as you

User · Answer

This is what worked for me   git remote set-url origin https   username github com username reponame git   Example   git remote set-url origin https   jsmith github com jsmith master git

User · Answer

List your current SSH keys  ls -l    ssh  Generate a new SSH key  ssh-keygen -t ed25519 -C  quot your email example com quot   where you should replace your email example com with your GitHub email address  When prompted to Enter a file in which to save the key  press Enter  Upon Enter passphrase  empty for no passphrase  - just press Enter  for an empty passphrase   List the your SSH keys again  ls -l    ssh  The files id ed25519 and id ed25519 pub should now have been added  Start the ssh-agent in the background  eval   ssh-agent -s   Add your SSH private key to the ssh-agent  ssh-add    ssh id ed25519  Next output the public key to the terminal screen  cat    ssh id ed25519 pub  Copy the output to the clipboard  Ctrl   Insert   Go to https   github com  lt your-github-username gt  and sign in with your username and password  Click your GitHub avatar in the upper-right corner  and then Settings  In the left pane click SSH and GPG keys  Click the green-colored button New SSH key and paste the public SSH key into the textarea labeled Key  Use a descriptive Title that tells from what computer you will use this SSH key  Click Add SSH key   If your current local repository was created with http and username  it needs to be recreated it so as to become SSH compatible  First check to make sure that you have a clean working tree so that you don t lose any work  git status  Then cd    to the parent directory and rm -fr  lt name-of-your-repo gt   Finally clone a fresh copy that uses SSH instead of username password  git clone git github com  your-github-username   repository-name  git  References  https   docs github com en free-pro-team latest github authenticating-to-github generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent https   docs github com en free-pro-team latest github authenticating-to-github adding-a-new-ssh-key-to-your-github-account

User · Answer

If you are using Git  for example  Git Bash  under Windows   and if you don t want to switch from HTTPS to SSH   you could also use Git Credential Manager for Windows  This application will keep the username and password for you

User · Answer

Here s another option   Instead of writing  git push origin HEAD   You could write   git push https   user pass yourrepo com path HEAD   Obviously  with most shells this will result in the password getting cached in history  so keep that in mind

User · Answer

If you ve got 2FA enabled on your Github account  your regular password won t work for this purpose  but you can generate a Personal Access Token and use that in its place instead   Visit the Settings -  Developer Settings -  Personal Access Tokens page in GitHub  https   github com settings tokens new   and generate a new Token with all Repo permissions     The page will then display the new token value  Save this value and use it in place of your password when pushing to your repository on GitHub    gt  git push origin develop Username for  https   github com    lt your username gt  Password for  https    lt your username gt  github com    lt your personal access token gt

User · Answer

A common cause is cloning using the default  HTTPS  instead of SSH  You can correct this by going to your repository  clicking  Clone or download   then clicking the  Use SSH  button above the URL field and updating the URL of your origin remote like this   git remote set-url origin git github com username repo git   This is documented at GitHub  Switching remote URLs from HTTPS to SSH

User · Answer

I just came across the same problem  and the simplest solution I found was to use SSH URL instead of HTTPS one   ssh   git github com username repo git   And not this   https   github com username repo git   You can now validate with just the SSH key instead of the username and password

User · Answer

For the uninitiated who are confused by the previous answers  you can do   git remote -v   Which will respond with something like  origin    https   yourname github com yourname yourrepo git  fetch  origin    https   yourname github com yourname yourrepo git  push    Then you can run the command many other have suggested  but now you know yourname and yourrepo from above  so you can just cut and paste yourname yourrepo git from the above into   git remote set-url origin git github com yourname yourrepo git

User · Answer

You basically have two options   If you use the same user on both machines you need to copy the  pub key to your PC  so GitHub knows that you are the same user   If you have created a new  pub file for your PC and want to treat the machines as different users  you need to register the new  pub file on the GitHub website   If this still doesn t work it might be because ssh is not configured correctly and that ssh fail to find the location of your keys  Try  ssh -vv username github com   To get more information why SSH fails

User · Answer

Permanently authenticating with Git repositories Run the following command to enable credential caching    git config credential helper store   git push https   github com owner repo git  Username for  https   github com    lt USERNAME gt  Password for  https   USERNAME github com    lt PASSWORD gt    You should also specify caching expire  git config --global credential helper  cache --timeout 7200   After enabling credential caching  it will be cached for 7200 seconds  2 hour

User · Answer

If you have cloned HTTPS instead of SSH and facing issue with username and password prompt on pull  push and fetch  You can solve this problem simply for UBUNTU  Step 1  move to root directory  cd      create a file  git-credentials  Add this content to that file with you usename password and githosting URL  https   user pass example com   Then execute the command  git config --global credential helper store   Now you will be able to pull push and fetch all details from your repo without any hassle

User · Answer

I had the same issue   So I changed the  git config file from my project   url   https   github com  lt your-user-here gt   lt your-repo-here gt    to  url   git github com  lt your-user-here gt   lt your-repo-here gt    and added the SSH public key to the Git profile which is in setting   For the SSH public key   cat    ssh id rsa pub

User · Answer

Update for HTTPS   GitHub has launched a new program for Windows that stores your credentials when you re using HTTPS   To use    Download the program from here Once you run the program  it will edit your  gitconfig file  Recheck if it edited the correct  gitconfig in case you have several of them  If it didn t edit the correct one  add the following to your  gitconfig   credential      helper     C   Path  To  Your  Downloaded  File  git-credential-winstore exe    NOTE the line break after  credential   It is required  Open up your command line client and try git push origin master once  If it asks you for a password  enter it and you re through  Password saved

User · Answer

If the SSH key or  netrc file did not work for you  then another simple  but less secure solution  that could work for you is git-credential-store - Helper to store credentials on disk   git config --global credential helper store   By default  credentials will be saved in file    git-credentials  It will be created and written to   Please note using this helper will store your passwords unencrypted on disk  protected only by filesystem permissions  If this may not be an acceptable security tradeoff

User · Answer

gen  the pub and priv keys    use  quot strange quot  naming convention  because those WILL BE more than 10      ssh-keygen -t rsa -b 4096 -C  quot me corp com quot  -f    ssh id rsa me corp com  hostname -s      set the git alias ONLY this shell session  alias git  GIT SSH COMMAND  quot ssh -i    ssh id rsa me corp com  hostname -s  quot  git      who did what when and why  git log --pretty --format   h  ai   lt  15  ae      s      set the git msg  export git msg  issue-123 my important commit msg      add all files   danger       and commit them with the msg  git add --all   git commit -m  quot  git msg quot  --author  quot Me  lt me corp com quot      finally   git push

User · Answer

You can cache your GitHub password in Git   Just follow the instructions from GitHub s official documentation   After following the instructions from the above link  you should be able to push pull to from your repository without typing your username password every time

User · Answer

For Windows Git users  after running git config --global credential helper store  if it still prompts for a password  you d better check where the configuration file is written to  using this command  git config --list --show-origin   In my case  after manually editing configuration file  C  Program Files Git mingw64 etc gitconfig   and adding the following text  it worked    credential      helper   store

User · Answer

Source  Set Up Git  The following command will save your password in memory for some time  for Git 1 7 10 or newer      git config --global credential helper cache   Set git to use the credential memory cache    git config --global credential helper  cache --timeout 3600    Set the cache to timeout after one hour  setting is in seconds

User · Answer

As many users has said  you just have to change your Git repository URL from HTTPS to SSH   If you haven t generated a SSH key in your machine  then your are going to have to do it   Just as an additional information  after doing this change I still was getting the same error       Permission Denied     In my case  the problem was that I was using the Windows Shell to execute the ngh command  since this command should open a prompt to request the SSH phrase and the Windows Shell doesn t open these kinds of prompts  the authentication just failed   So  I just had to open the Git shell and execute the ngh command there  put the SSH phrase in the prompt every time it asked for it and  voil       It just worked fine

[authentication] Git push requires username and password

Examples related to authentication

Examples related to github

Examples related to git-push

Examples related to git-pull

Examples related to git-clone