Firefox strict privacy mode prevents codespaces from loading

[milesburton]

Select Topic Area

Product Feedback

Body

Issue Summary: GitHub Codespaces browser access blocked by Firefox Strict Privacy settings

Diagnosis steps:

Tested DNS and connectivity to core GitHub services
Identified 404s on assets.github.dev
Found 401 errors on tunnels API
Verified VS Code desktop client worked
Isolated issue to Firefox Strict Privacy settings

Root cause:
Firefox Strict Privacy mode blocks cross-origin requests required by GitHub Codespaces browser editor.

Solution:
Either:

Switch to Standard Privacy mode in Firefox by visiting about:preferences#privacy

or

Add exceptions for required domains:

github.dev
github.com
visualstudio.com
githubusercontent.com

Hope that helps

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

[jbclements]

Also see helpful information at https://github.com/orgs/community/discussions/124964 and https://github.com/orgs/community/discussions/42091 . It may not be necessary to whitelist all four of these domains?

[jbclements]

Indeed, it appears (after a very limited amount of testing) that whitelisting github.dev may in fact be enough to make this fly.