ERROR: Permission to [some-git-repo].git denied to BG-JIB










2















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?










share|improve this question






















  • Did you check if you had the private key loaded to the agent?

    – Praveen P
    Nov 11 '18 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 '18 at 21:25











  • Hmmm, is BG-JIB the GitHub user that has the repo?

    – Praveen P
    Nov 11 '18 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 '18 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 '18 at 21:43















2















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?










share|improve this question






















  • Did you check if you had the private key loaded to the agent?

    – Praveen P
    Nov 11 '18 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 '18 at 21:25











  • Hmmm, is BG-JIB the GitHub user that has the repo?

    – Praveen P
    Nov 11 '18 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 '18 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 '18 at 21:43













2












2








2


1






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?










share|improve this question














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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 11 '18 at 18:36









1shooperman1shooperman

113




113












  • Did you check if you had the private key loaded to the agent?

    – Praveen P
    Nov 11 '18 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 '18 at 21:25











  • Hmmm, is BG-JIB the GitHub user that has the repo?

    – Praveen P
    Nov 11 '18 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 '18 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 '18 at 21:43

















  • Did you check if you had the private key loaded to the agent?

    – Praveen P
    Nov 11 '18 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 '18 at 21:25











  • Hmmm, is BG-JIB the GitHub user that has the repo?

    – Praveen P
    Nov 11 '18 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 '18 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 '18 at 21:43
















Did you check if you had the private key loaded to the agent?

– Praveen P
Nov 11 '18 at 19:23






Did you check if you had the private key loaded to the agent?

– Praveen P
Nov 11 '18 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 '18 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 '18 at 21:25













Hmmm, is BG-JIB the GitHub user that has the repo?

– Praveen P
Nov 11 '18 at 21:28






Hmmm, is BG-JIB the GitHub user that has the repo?

– Praveen P
Nov 11 '18 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 '18 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 '18 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 '18 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 '18 at 21:43












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
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%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

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































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.




draft saved


draft discarded














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





















































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

𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

Edmonton

Crossroads (UK TV series)