Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
I did have my repo under my personal account KerryJones/hubhaus, but I've created an organization and moved it to HubHaus/hubhaus. This, as expected, broke a ton of things. I've fixed everything except Envoyer.
I'm getting a ton of these errors: Unable To Connect To Code Provider
When I go to Project Settings > Source Control and change the repo, it gives me this error:
Whoops! There were some problems with your input.
Invalid repository. Are you sure you have access to it?
It doesn't tell me how to provide access to it. My personal account still does.
If I go to my "Account > Integrations" and click "Refresh Github Token" it simply tells me I've connected with GitHub.
Any advice? This is a production environment.
@kerryjones It could be either of two things. First, the easy way, delete the ssh key on forge server, delet server from Envoyer and add again and save the key from Envoyer again to forge. I have had this work but only once in a while. The other is to nuke the site in Envoyer and recreate it with the new repo.
OK, I know this is 2 years old but it is brand new to me. I solved this by changing the Third-party application access policy on my GItHub organization. Hope it saves someone else the headache.
Legend, you just saved me a world of pain!
Much appreciated <3
@digitalagua thank you, that did the trick! :)
@digitalagua Thank you!
I know this is old, but I've been searching for hours after having this issue once in the past and forgetting. It's not perfect as it opens restrictions, but at this point, I'm tired of being frustrated with it. Thanks again @digitalagua
Unfortunately, this still seems to be a problem and bit me today. We migrated a private GH repo to an organization (growing project) and Envoyer will NOT forget my previous credentials. Unlink. Fine. Connect to Github... "connected!" without ever asking me to reconnect with new credentials. This seems like an ongoing bug, but unsure how to get around it, other than "remove all 3rd party restrictions". :/
Please or to participate in this conversation.