Persistent "token expired or invalid: 403" Error on Copilot #165647
Replies: 5 comments 2 replies
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
I was using the model Claude Sonnet 4, it worked for me when I changed the model to Claude Sonnet 3.7 |
Beta Was this translation helpful? Give feedback.
-
|
Been having the same problem today as well. Sooooo annoying |
Beta Was this translation helpful? Give feedback.
-
|
me too |
Beta Was this translation helpful? Give feedback.
-
|
i have the same problem |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Copilot Feature Area
VS Code
Body
Hello GitHub Team,
I am experiencing a persistent "token expired or invalid: 403" error with GitHub Copilot. My GitHub username is mibnua7.
The full error message is: "Sorry, your request failed. Please try again. Request id: [TULIS REQUEST ID TERBARU DARI ERROR ANDA]. Reason: token expired or invalid: 403"
This is not a network or simple configuration issue. I have already tried all the standard troubleshooting steps, including:
Signing out and signing back into VS Code.
Revoking OAuth app access on my GitHub settings page.
Completely uninstalling and reinstalling the Copilot and Copilot Chat extensions.
Clearing all GitHub-related credentials from my OS (Windows Credential Manager / macOS Keychain).
Testing on a completely different network (mobile hotspot), and the error still persists.
None of these steps have solved the problem. It seems to be a server-side or account-specific bug.
Could you please investigate the failed request ID to determine the root cause?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions