GitHub Codespace cannot be opened – Failed to connect to relay URL (Code: 1006)

[duyphanbosch]

🏷️ Discussion Type

Bug

Body

Hello GitHub Support,

I am unable to open/connect to my GitHub Codespace from the browser.

Codespace:

• Permanent Codespace name: improved-space-memory-jj7565v999jw2p7qv
• URL: https://improved-space-memory-jj7565v999jw2p7qv.github.dev

Error message:
"Failed to connect to relay url Code: 1006 Reason:
(connection rejected by browser)"

The browser displays:
"Oh no, something unexpected went wrong!
Refreshing your window may fix this error."

I have tried:

• Refreshing the Codespace page
• Using the "Retry connecting to the codespace" button
• Reconnecting to the Codespace

However, the issue persists.

Expected behavior:
The Codespace should open normally and establish the VS Code web connection.

Actual behavior:
The Codespace fails to establish the connection and shows error code 1006 when connecting to the relay URL.

Could you please check whether there is any issue with this Codespace or the Codespaces relay/connection service on your side?

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

[TongyiDai]

Code 1006 means the browser WebSocket/relay connection closed abnormally; it does not by itself show whether the codespace VM is unhealthy. Separate browser-path failure from codespace failure before rebuilding anything:

1. Open https://github.com/codespaces and launch the same named codespace from there. Confirm it is listed under the same account.
2. Try a current Chrome or Edge session with extensions disabled, then a different network. Corporate proxies, VPNs, TLS inspection, and WebSocket filtering are common differentiators for relay failures.
3. Test the non-browser path: gh codespace view -c improved-space-memory-jj7565v999jw2p7qv and, if it is running, gh codespace ssh -c improved-space-memory-jj7565v999jw2p7qv. If SSH works while the browser fails, preserve the codespace and focus on browser/network relay access.
4. If both paths fail, collect gh codespace logs -c improved-space-memory-jj7565v999jw2p7qv plus the browser console/network errors before considering a rebuild.

Do not delete the codespace as an early troubleshooting step, especially if it contains unpushed work. GitHub's connection guide: https://docs.github.com/en/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces