ERROR: Permission to [some-git-repo].git denied to BG-JIB
up vote
2
down vote
favorite
I was recently trying to push a public repository that I am the sole contributor on (it's for a MOOC I am taking) and I got an error I've never seen before:
$ git push
ERROR: Permission to my-fanch-repo.git denied to BG-JIB.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
The strange part is that I was able to both push and pull as recently as a week ago. I double checked my ssh keys and verified that I hadn't renamed my repo and forgotten to update my local remotes. I even tried to re-add my public ssh key to github (NOTE: it gave me the "already in use" message).
My next step was to reboot the Mac (High Sierra 10.13.6) and try again. On that next attempt, I got an error I recognize:
$ git push -u origin master
identity_sign: private key /path/to/private_key contents do not match public
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
On a whim, I ran the same command a second time and was back to square one:
$ git push -u origin master
ERROR: Permission to my-fancy-repo.git denied to BG-JIB.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I tried cloning the repo again in a completely separate directory and received the same message. In the end, I deleted my existing public key on github and added a newly generated one. This solved the issue.
While I am happy that the issue is resolved, it feels more like a "hammer" than a real solution.
What does the BG-JIB error mean? Is there a better solution?
git github ssh-keys
asked Nov 11 at 18:36
1shooperman
113
add a comment |
up vote
2
down vote
favorite
I was recently trying to push a public repository that I am the sole contributor on (it's for a MOOC I am taking) and I got an error I've never seen before:
$ git push
ERROR: Permission to my-fanch-repo.git denied to BG-JIB.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
The strange part is that I was able to both push and pull as recently as a week ago. I double checked my ssh keys and verified that I hadn't renamed my repo and forgotten to update my local remotes. I even tried to re-add my public ssh key to github (NOTE: it gave me the "already in use" message).
My next step was to reboot the Mac (High Sierra 10.13.6) and try again. On that next attempt, I got an error I recognize:
$ git push -u origin master
identity_sign: private key /path/to/private_key contents do not match public
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
On a whim, I ran the same command a second time and was back to square one:
$ git push -u origin master
ERROR: Permission to my-fancy-repo.git denied to BG-JIB.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I tried cloning the repo again in a completely separate directory and received the same message. In the end, I deleted my existing public key on github and added a newly generated one. This solved the issue.
While I am happy that the issue is resolved, it feels more like a "hammer" than a real solution.
What does the BG-JIB error mean? Is there a better solution?
git github ssh-keys
asked Nov 11 at 18:36
1shooperman
113
Did you check if you had the private key loaded to the agent?
– Praveen P
Nov 11 at 19:23
Thanks for the clarifying question! I did (and apologize for not adding that detail!). I double checked that the agent was running and that it had the keys I expected both before and after the system restart.
– 1shooperman
Nov 11 at 21:25
Hmmm, is BG-JIB the GitHub user that has the repo?
– Praveen P
Nov 11 at 21:28
BG-JIB isn't a user attached to the repo or the system. I am the only person to use this computer since I did a clean install of high sierra when it came out. I am both the owner and sole contributor to the repository. EDIT: (As a long shot) since this a work computer, I also reached out to our infrastructure manager to see if this was some kind of network middleware that could be corrupting my keys. He did not recognize it either.
– 1shooperman
Nov 11 at 21:31
It's strange that you got two completely different errors (public key denied and repo not found) at the same time. Sorry I have no idea why this happened now. Just like connection closed by peer error that no one knows why its happening.
– Praveen P
Nov 11 at 21:43
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I was recently trying to push a public repository that I am the sole contributor on (it's for a MOOC I am taking) and I got an error I've never seen before:
$ git push
ERROR: Permission to my-fanch-repo.git denied to BG-JIB.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
The strange part is that I was able to both push and pull as recently as a week ago. I double checked my ssh keys and verified that I hadn't renamed my repo and forgotten to update my local remotes. I even tried to re-add my public ssh key to github (NOTE: it gave me the "already in use" message).
My next step was to reboot the Mac (High Sierra 10.13.6) and try again. On that next attempt, I got an error I recognize:
$ git push -u origin master
identity_sign: private key /path/to/private_key contents do not match public
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
On a whim, I ran the same command a second time and was back to square one:
$ git push -u origin master
ERROR: Permission to my-fancy-repo.git denied to BG-JIB.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I tried cloning the repo again in a completely separate directory and received the same message. In the end, I deleted my existing public key on github and added a newly generated one. This solved the issue.
While I am happy that the issue is resolved, it feels more like a "hammer" than a real solution.
What does the BG-JIB error mean? Is there a better solution?
git github ssh-keys
asked Nov 11 at 18:36
1shooperman
113
I was recently trying to push a public repository that I am the sole contributor on (it's for a MOOC I am taking) and I got an error I've never seen before:
$ git push
ERROR: Permission to my-fanch-repo.git denied to BG-JIB.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
The strange part is that I was able to both push and pull as recently as a week ago. I double checked my ssh keys and verified that I hadn't renamed my repo and forgotten to update my local remotes. I even tried to re-add my public ssh key to github (NOTE: it gave me the "already in use" message).
My next step was to reboot the Mac (High Sierra 10.13.6) and try again. On that next attempt, I got an error I recognize:
$ git push -u origin master
identity_sign: private key /path/to/private_key contents do not match public
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
On a whim, I ran the same command a second time and was back to square one:
$ git push -u origin master
ERROR: Permission to my-fancy-repo.git denied to BG-JIB.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I tried cloning the repo again in a completely separate directory and received the same message. In the end, I deleted my existing public key on github and added a newly generated one. This solved the issue.
While I am happy that the issue is resolved, it feels more like a "hammer" than a real solution.
What does the BG-JIB error mean? Is there a better solution?
git github ssh-keys
git github ssh-keys
asked Nov 11 at 18:36
1shooperman
113
asked Nov 11 at 18:36
1shooperman
113
asked Nov 11 at 18:36
1shooperman
113
asked Nov 11 at 18:36
1shooperman
113
asked Nov 11 at 18:36
1shooperman
113
113
Did you check if you had the private key loaded to the agent?
– Praveen P
Nov 11 at 19:23
Thanks for the clarifying question! I did (and apologize for not adding that detail!). I double checked that the agent was running and that it had the keys I expected both before and after the system restart.
– 1shooperman
Nov 11 at 21:25
Hmmm, is BG-JIB the GitHub user that has the repo?
– Praveen P
Nov 11 at 21:28
BG-JIB isn't a user attached to the repo or the system. I am the only person to use this computer since I did a clean install of high sierra when it came out. I am both the owner and sole contributor to the repository. EDIT: (As a long shot) since this a work computer, I also reached out to our infrastructure manager to see if this was some kind of network middleware that could be corrupting my keys. He did not recognize it either.
– 1shooperman
Nov 11 at 21:31
It's strange that you got two completely different errors (public key denied and repo not found) at the same time. Sorry I have no idea why this happened now. Just like connection closed by peer error that no one knows why its happening.
– Praveen P
Nov 11 at 21:43
add a comment |
Did you check if you had the private key loaded to the agent?
– Praveen P
Nov 11 at 19:23
Thanks for the clarifying question! I did (and apologize for not adding that detail!). I double checked that the agent was running and that it had the keys I expected both before and after the system restart.
– 1shooperman
Nov 11 at 21:25
Hmmm, is BG-JIB the GitHub user that has the repo?
– Praveen P
Nov 11 at 21:28
BG-JIB isn't a user attached to the repo or the system. I am the only person to use this computer since I did a clean install of high sierra when it came out. I am both the owner and sole contributor to the repository. EDIT: (As a long shot) since this a work computer, I also reached out to our infrastructure manager to see if this was some kind of network middleware that could be corrupting my keys. He did not recognize it either.
– 1shooperman
Nov 11 at 21:31
It's strange that you got two completely different errors (public key denied and repo not found) at the same time. Sorry I have no idea why this happened now. Just like connection closed by peer error that no one knows why its happening.
– Praveen P
Nov 11 at 21:43
Did you check if you had the private key loaded to the agent?
– Praveen P
Nov 11 at 19:23
Did you check if you had the private key loaded to the agent?
– Praveen P
Nov 11 at 19:23
Thanks for the clarifying question! I did (and apologize for not adding that detail!). I double checked that the agent was running and that it had the keys I expected both before and after the system restart.
– 1shooperman
Nov 11 at 21:25
Thanks for the clarifying question! I did (and apologize for not adding that detail!). I double checked that the agent was running and that it had the keys I expected both before and after the system restart.
– 1shooperman
Nov 11 at 21:25
Hmmm, is BG-JIB the GitHub user that has the repo?
– Praveen P
Nov 11 at 21:28
Hmmm, is BG-JIB the GitHub user that has the repo?
– Praveen P
Nov 11 at 21:28
BG-JIB isn't a user attached to the repo or the system. I am the only person to use this computer since I did a clean install of high sierra when it came out. I am both the owner and sole contributor to the repository. EDIT: (As a long shot) since this a work computer, I also reached out to our infrastructure manager to see if this was some kind of network middleware that could be corrupting my keys. He did not recognize it either.
– 1shooperman
Nov 11 at 21:31
BG-JIB isn't a user attached to the repo or the system. I am the only person to use this computer since I did a clean install of high sierra when it came out. I am both the owner and sole contributor to the repository. EDIT: (As a long shot) since this a work computer, I also reached out to our infrastructure manager to see if this was some kind of network middleware that could be corrupting my keys. He did not recognize it either.
– 1shooperman
Nov 11 at 21:31
It's strange that you got two completely different errors (public key denied and repo not found) at the same time. Sorry I have no idea why this happened now. Just like connection closed by peer error that no one knows why its happening.
– Praveen P
Nov 11 at 21:43
It's strange that you got two completely different errors (public key denied and repo not found) at the same time. Sorry I have no idea why this happened now. Just like connection closed by peer error that no one knows why its happening.
– Praveen P
Nov 11 at 21:43
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- 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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53251911%2ferror-permission-to-some-git-repo-git-denied-to-bg-jib%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Did you check if you had the private key loaded to the agent?
– Praveen P
Nov 11 at 19:23
Thanks for the clarifying question! I did (and apologize for not adding that detail!). I double checked that the agent was running and that it had the keys I expected both before and after the system restart.
– 1shooperman
Nov 11 at 21:25
Hmmm, is BG-JIB the GitHub user that has the repo?
– Praveen P
Nov 11 at 21:28
BG-JIB isn't a user attached to the repo or the system. I am the only person to use this computer since I did a clean install of high sierra when it came out. I am both the owner and sole contributor to the repository. EDIT: (As a long shot) since this a work computer, I also reached out to our infrastructure manager to see if this was some kind of network middleware that could be corrupting my keys. He did not recognize it either.
– 1shooperman
Nov 11 at 21:31
It's strange that you got two completely different errors (public key denied and repo not found) at the same time. Sorry I have no idea why this happened now. Just like connection closed by peer error that no one knows why its happening.
– Praveen P
Nov 11 at 21:43