Repository navigation
GitHub repository "Bad credentials" #5808
Replies: 3 comments 1 reply
|
"Bad credentials" is GitHub's own error message: the token draw.io saved for your GitHub account is no longer valid (revoked, expired, or the draw.io app was de-authorized). draw.io doesn't ask for a password, so there's nothing to check on its side. You just need a new token:
|
|
Ahh, I couldn't find the account name in the top-right corner. Therefore, I couldn't use it to Sign out under the GitHub entry. But clearing the site data for app.diagrams.net did the trick. Thank you, Pierre!
Kind regards,
Joaquin
…________________________________
De: Pierre ***@***.***>
Enviado: lunes, 19 de octubre de 2026 13:34
Para: jgraph/drawio ***@***.***>
Cc: JoaquinAmeller ***@***.***>; Author ***@***.***>
Asunto: Re: [jgraph/drawio] GitHub repository "Bad credentials" (Discussion #5808)
"Bad credentials" is GitHub's own error message: the token draw.io saved for your GitHub account is no longer valid (revoked, expired, or the draw.io app was de-authorized). draw.io doesn't ask for a password, so there's nothing to check on its side. You just need a new token:
1. In draw.io, click your account name in the top-right corner. In the panel that opens, use Sign out under the GitHub entry. (If you can't get to it, clearing the site data for app.diagrams.net does the same thing.)
2. Open the file again (File → Open from → GitHub). draw.io asks you to authorize it again on GitHub, which creates a fresh token.
3. If the repository belongs to an organization, check github.com/settings/applications<https://github.com/settings/applications> → Authorized OAuth Apps → draw.io. The organization must have granted access (or you can click Request there), otherwise GitHub refuses access to that org's repos even with a valid login.
—
Reply to this email directly, view it on GitHub<#5808?email_source=notifications&email_token=ASKTKJWUNUM5E42PYFDGPHL5UX34DA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJQGM4DSMJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-19038911>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASKTKJR7XU4IZDE2IU6Q3C35UX34DAVCNFSNUABHKJSXA33TNF2G64TZHM3DONJQHA2DEOB3IRUXGY3VONZWS33OHMYTCMBXGIYDGMFBOYBA>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/ASKTKJSWNFYBZ3LOSWL27Q35UX34DA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJQGM4DSMJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android<https://github.com/notifications/mobile/android/ASKTKJREHTXOY5XXRW2DETD5UX34DA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJQGM4DSMJRUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today!
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Clearing the site data was the right fix here. The account panel wouldn't have helped: its GitHub entry with Sign out only appears after draw.io has loaded your GitHub profile, and loading the profile is the request GitHub was rejecting with "Bad credentials". So there was no GitHub entry to sign out of. draw.io also keeps a "remember me" flag for GitHub in the browser's storage. This error doesn't clear that flag, so every attempt went back through the same remembered sign-in instead of asking you to authorise draw.io again. Removing the site data removed the flag, and the next attempt started a fresh authorisation. If you find this thread because you have the same error: clearing the site data for app.diagrams.net also deletes diagrams saved to Browser storage, your Extras > Configuration settings and the scratchpad, so export anything you need from those first. To check that a fresh sign-in works before you clear anything, open the file from GitHub in a private window. Notes for maintainersReporter is unblocked (clearing site data for app.diagrams.net fixed it). Same symptom and same fix as #5298 (closed for missing info, where people also cleared the cache or used a private window). Why users get stuck (mirror at 17b367b, 32.5.5):
Not confirmed: what production's Possible fix: in the Automated first response by the draw.io triage bot. |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
Cannot open my diagram hosted in my own GitHub repository. I receive a "bad credentials" message, but I don't even find where to check these credentials.. Can anyone help me with this?
All reactions