You’re right that that shouldn’t apply when using SSH, tokens are for Git over HTTPS. I wonder if that repository happens to use HTTPS, maybe with a cached password, for some reason? You can use git remote show origin to check (assuming your remote is named origin, which is the default for where you cloned from).

nope, does not use https
and I see others are having issue now even with the token

Hey @sglanger 👋 and @airtower-luna 👋

From my understanding of the blog post referenced, the concern is that password authentication for Git operations over SSH should have worked during this scheduled brownout. Is that right?

I’m not sure I understand the same, and would have expected the git pushed to fail, if using pw auth.

For how to setup your SSH key, docs begin here:

https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh

Though it was mentioned that other users are/were having issues with a valid SSH token, and receiving the same message back? Could you link us to an example thread?

other examples

<a href="https://github.community/t/all-3rd-party-connection-to-github-failed-with-403/192601">All 3rd party connection to Github failed with 403</a> <a class="badge-wrapper  bullet" href="/c/github-ecosystem/37"><span class="badge-category-bg" style="background-color: #28a745;"></span><span style="" data-drop-close="true" class="badge-category clear-badge" title="Discussion and support using GitHub’s REST, and GraphQL APIs, building Applications and OAuth Apps, the GitHub Marketplace, and third party integrations.">GitHub Ecosystem</span></a>

I use sourcetree and connect to github via basic auth (already use personal access token as password) but today I can’t pull from origin with error 403 but I can pull form git CLI with same token and I use webhook in my repository, but today it got same 403 error too Can someone has any suggestion for me

But never mind, today it works again

PS: Nethgato, you mentioned this was a “scheduled” brownout. Where was that announcement posted? I missed it, and it does not mention it was scheduled in the error I first posted.

Thx, it would have been useful to have that info in the error message from yesterday. The blog link that was included in the error did not have the Brownout schedule in it.

@sglanger you’re right:

it would have been useful to have that info in the error message from yesterday. The blog link that was included in the error did not have the Brownout schedule in it.

I was disappointed to see that the blog post that did not include the specific time and date, but the initial plan. We’ve elevated that detail to our dev team to consider for the future.

For the auth failing with token based auth, that experience seems to be unrelated to the scheduled brown out for pw based auth.

I’d be willing to bet that if you compare the number of accounts on github and compare to the number who have read that post, it will be a rather large difference.

Token authentication requirements for Git operations | The GitHub Blog

Hello,
did I miss something? That date is nine days ahead, but if I want to login in community, always have to post token.
The correct date is 2020?

Regards

The linked post is about Git operations, not logging in to GitHub or the community forum (here). Where to you have to post a token to log in here?

Hello,
Wird verarbeitet: Captura de pantalla de 2021-08-06 15-10-06.png …
always happens.

Regards

That looks like you tried to post a picture (screenshot, maybe?) but it didn’t work. Could you try again?

Hello,
yes, it is a screenshot, but this is only one more difficulty for me because using a old browser-version.

Regards

Wird verarbeitet: Captura de pantalla de 2021-08-06 15-10-06.png …

Hello,
doesn’t work:
" Entschuldige, es gab einen Fehler beim Hochladen der Datei. Bitte versuche es noch einmal.

[OK]"

Regards

Hello,
to login I have to do 2 way indent.
Images-posting for mi is working again.

Regards

Captura de pantalla de 2021-08-14 16-15-561000×431 24 KB

Here (community) all working fine.

Regards

That’s normal if you’re logging in without 2FA. You should have received the code by email. That has nothing to do with the PAT you need for Git operations over HTTPS, though.