New Feature: Connectivity v2 feedback #112351
Replies: 4 comments 3 replies
-
Hello @vincentmaxwell 👋 ! I'm sorry for the friction caused here. In order to debug this further, do you see anything in the Network tab of the Developer tools in the browser? Or any errors in the console? There should be some sort of indication of how the requests are being denied. Also, are you able to connect on any other network such as your wifi connection at home? |
Beta Was this translation helpful? Give feedback.
-
Not to "me too" but ... me too. I have to tell my students to disable this, as allow-listing the URL in the documentation doesn't do anything different. |
Beta Was this translation helpful? Give feedback.
-
I have been experiencing issues and being unable to connect both via multiple browser and VSCode app when Connectivity v2 was enabled. I have now disabled it so that I can continue working, however if you need me to provide any diagnostics please reach out. Not sure what to report here. |
Beta Was this translation helpful? Give feedback.
-
The feature preview cannot be disabled anymore, as GitHub has removed the option before even this thread was resolved. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
Hello, I was using codespaces to teach my students at my school however since v2 launched in February, the feature prevented us from launching our codespaces. Our IT department whitelisted all domains and redirects, but I am still experiencing issues. At first the codespace would give an error screen saying the device was offline. Then after IT checked the webfilter and allowed redirects it is loading slowly and the console output is several errors regarding the relay. The error message it displays is:
Failed to connect to relay url Code 1006 Reason: connection rejected by browser
I have ensured that redirects on the browser are allowed for the site permissions and have tested different browsers. The IT department also assures me the webfilter is not causing this issue so I am at a loss?
The workaround currently is to disable the v2 connectivity feature.
Beta Was this translation helpful? Give feedback.
All reactions