Problems with CS50 Codespace

[johnReeferVermont]

Select Topic Area

Bug

Body

Hello
I am having a lot of problems loading codespaces, either through a browser or directly through VS Code. I use NETGEAR Armor Bitdefender for protection and unless I turn it off completely, it will not load.

When I attempt to load it, it will begin to load and then sit forever while it loads the workspace. I notice that it appears to want me to authorize CS50 again and again although if I do, it will try to reload and sit in the same place. Same symptoms if I choose to open in VS Code.

I have added to rules and exceptions all of the sites that I am supposed to add. I have excluded the ports both in Chrome as well as in the VSCode executable. Nothing works.

If I turn off my firewall, it will not load. If I turn off Online Threat Defense, it will not load. If I turn off firewall, Online Threat Defense, Vulnerability and Advance threat defense, then it loads fine. I have open cases with Bitdefender but they have not really helped me.

I am running Windows 11 64 bit.

While I am a little technical, I am not technical enough to understand if I would be better of using a different protocol?. There is something I am not excluding properly since I am able to load it fine when all of Bitdefender is turned off. Of course, that leaves me completely vulnerable to attacks. Is there any specific documentation for NETGEAR Armor Bitdefender?

Thank you for any assistance.

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

[johnReeferVermont]

Not feedback. It is a bug