I created the private repo examplesite/myprivaterepo using the Github UI from my browser.
Then I went to my go directory (on the desktop) and cloned it:
$ cd $GOPATH
$ go get So far so good. Created the file scheduler.go, added to repo, and pushed.
$ vim scheduler.go
$ git add scheduler.go
$ git commit
$ git pushEverythng's OK. But when I went to a clean laptop and tried to clone the repo, I got an error:
# Now on laptop, which doesn't yet know about the repo
$ cd $GOPATH
$ go get
# At this point it should ask for my user ID and password ,right? But it doesn't.
# Instead, this error occurs:
cd .; git clone /Users/tom/go/src/
Cloning into '/Users/tom/go/src/
fatal: could not read Username for ' terminal prompts disabled
package exit status 128Why is my laptop hating on my own repo and how can I get it to accept its fate? Thanks.
612 Answers
I found this extremely helpful, and it solved my problem. This command will allow your 2FA to do its thing (and save you the trouble of entering your username and password):
For Github:
git config --global --add url.":".insteadOf ""For Gitlab:
git config --global --add url.":".insteadOf ""Source:
If you're not using 2FA, you can still use SSH and this will work.
Resulting .gitconfig will be like:
[url ":"] insteadOf = go get disables the "terminal prompt" by default. This can be changed by setting an environment variable of git:
env GIT_TERMINAL_PROMPT=1 go get It complains because it needs to use ssh instead of https but your git is still configured with https. so basically as others mentioned previously you need to either enable prompts or to configure git to use ssh instead of https. a simple way to do this by running the following:
git config --global --add url.":".insteadOf ""or if you already use ssh with git in your machine, you can safely edit ~/.gitconfig and add the following line at the very bottom
Note: This covers all SVC, source version control, that depends on what you exactly use, github, gitlab, bitbucket)
# Enforce SSH
[url "ssh://git@"] insteadOf =
[url "ssh://git@"] insteadOf =
[url "ssh://git@"] insteadOf = If you want to keep password pompts disabled, you need to cache password. For more information on how to cache your github password on mac, windows or linux, please visit this page.
For more information on how to add ssh to your github account, please visit this page.
Also, more importantly, if this is a private repository for a company or for your self, you may need to skip using proxy or checksum database for such repos to avoid exposing them publicly.
To do this, you need to set GOPRIVATE environment variable that controls which modules the go command considers to be private (not available publicly) and should therefore NOT use the proxy or checksum database.
The variable is a comma-separated list of patterns (same syntax of Go's path.Match) of module path prefixes. For example,
export GOPRIVATE=*.corp.example.com,Or
go env -w GOPRIVATE=- For more information on how to solve private packages/modules checksum validation issues, please read this article.
- For more information about go 13 modules and new enhancements, please check out Go 1.13 Modules Release notes.
One last thing not to forget to mention, you can still configure go get to authenticate and fetch over https, all you need to do is to add the following line to $HOME/.netrc
machine github.com login USERNAME password APIKEY- For GitHub accounts, the password can be a personal access tokens.
- For more information on how to do this, please check Go FAQ page.
I hope this helps the community and saves others' time to solve described issues quickly. please feel free to leave a comment in case you want more support or help.
31st -- go get will refuse to authenticate on the command line. So you need to cache the credentials in git. Because I use osx I can use osxkeychain credential helper.
2nd For me, I have 2FA enabled and thus could not use my password to auth. Instead I had to generate a personal access token to use in place of the password.
- setup osxkeychain credential helper
- If using TFA instead of using your password, generate a personal access token with repo scope
- git clone a private repo just to make it cache the password
git cloneand used your github.com username for username and the generated personal access token for password. Removed the just cloned repo and retest to ensure creds were cached --
git cloneand this time wasnt asked for creds.- go get will work with any repos that the personal access token can access. You may have to repeat the steps with other accounts / tokens as permissions vary.
If you just want go get to work real fast, and move along with your work...
Just export GIT_TERMINAL_PROMPT=1
$ export GIT_TERMINAL_PROMPT=1
$ go get [whatever]It will now prompt you for a user/pass for the rest of your shell session. Put this in your .profile or setup git as above for a more permanent solution.
From go 1.13 onwards, if you had already configured your terminal with the git credentials and yet facing this issue, then you could try setting the GOPRIVATE environment variable. Setting this environment variable solved this issue for me.
export GOPRIVATE= of the package}/* Add this is your bash_profile:
export GOPRIVATE=Then run:
git config --global --add url.":".insteadOf ""If you configure your gitconfig with this option, you will later have a problem cloning other repos of GitHub
git config --global --add url. "". Instead, ""Instead, I recommend that you use this option
echo "export GIT_TERMINAL_PROMPT=1" >> ~/.bashrc || ~/.zshrcand do not forget to generate an access token from your private repository. When prompted to enter your password, just paste the access token. Happy clone :)
While there are a lot of answers around using SSH authentication for GitHub, the question pertains to the correct usage for go modules. To this end, Luna Lovegood provides the right answer here.
To reiterate, by default Go tries to use a public repository to download packages. We need to specify that it authenticate using SSH for private repos. And to do this, the following can be used:
go env -w GOPRIVATE=
.
.
go mod vendor # this will now work for your private libGlob patterns also work, so if you have multiple private repositories, you can add
go env -w GOPRIVATE=Edit: Correct wording.
2I had the same problem on windows "error: failed to execute prompt script (exit code 1) fatal: could not read Username for '': No error" trying to login to github through the login dialog. When I canceled the dialog git asked me for login and password in the command line and it worked fine.
I faced this error terminal prompts disabled after changing my credentials, Carthage failed to update the dependencies and show this error on terminal.
I just did the simple following steps and it's started working...
- Remove old credentials from
keychain access - Tried to clone the same repo in different location.
- It asked for credentials (username + password) to set.
- And then Carthage update worked as before.
I tried adding this command
export GOPRIVATE=
and it worked for me
