Github OAuth fails about docker-code-server

[aasimenator]

I have the same issue, as per the documentation, I've generated the /config/.ssh/id_rsa & /config/.ssh/id_rsa.pub
/config/.ssh/id_rsa.pub was copied over to my GitHub > Settings > SSH and GPG keys > New SSH key

then I ran git config --global user.name "myusername" & git config --global user.email "myemailaddress"

then clicking on anything like "Publish to Github" takes me to an OAuth screen, and when I click continue I get an "Oh no! An error occurred!

[github-actions]

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

[Marnalas]

I have the exact same problem.

I tried to deactivate some securities thinking that maybe they were preventing the callbackUri to be called successfully : https://vscode-auth.github.com/authorize/?callbackUri=https://_subdomain.domain_/callback...

But nothing has worked so far.

Is your DNS record also managed by Cloudflare and proxied (not "DNS only") ?

[zhenry9]

My DNS is managed by cloudflare, but since it's the free version it doesn't proxy wildcard CNAMEs, which is where my code-server instance is running.

I too disabled all auth except for what's built-in to the container and got the same results. I also put my ssl certificate into the .ssh folder, same results. Not sure what else to try

[Marnalas]

I use Cloudflare for free too but I don't use a wildcard CNAME. That's why I get to have it proxied. But I also tried the "DNS only" option and, like you, it didn't work any better.

"I also put my ssl certificate into the .ssh folder, same results". It's not the ssl certificate that's supposed to go into the .ssh folder, it's the private part of the SSH key set in your github account (https://docs.github.com/en/authentication/connecting-to-github-with-ssh).
That being said I've done that when I first set up the container (I prefer this authentication to the PAT one) and it didn't work either.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[aptalca]

This should be fixed by upstream now. Feel free to reopen or report to them if not.