GitHub Codespaces stuck at “Setting up your codespace”

[surigangaraju-sudo]

🏷️ Discussion Type

Bug

Body

Hi everyone,

My GitHub Codespace is consistently stuck at “Setting up your codespace” and never opens.

I have tried the following:

• Stopped and restarted the Codespace.
• Deleted the old Codespace and created a new one.
• Tested in multiple browsers, including Ulaa and Firefox.
• Confirmed that my included Codespaces usage has not been exhausted.
• Confirmed that my repository does not contain a .devcontainer configuration.
• Created a completely new Blank Codespace from the GitHub template, and that also gets stuck at “Setting up your codespace.”
• My GitHub repository itself opens normally.
• There is no “View logs” option on the setup screen.

Since even a Blank Codespace gets stuck during setup, the issue does not appear to be specific to my repository.

Has anyone experienced this recently or know what could cause Codespaces to remain stuck during provisioning?

Any suggestions would be appreciated. Thank you!

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[jamalkamaladdin]

For diagnostics, run gh codespace logs locally and select your stuck codespace to request creation logs.
If none are available, open your setup tab's developer tools and capture Console errors.
See GitHub's logging guide for both options.