Users who are on a network that requires use of a proxy server to connect to external websites may experience problems using Live Share. Specifically, attempting to share using a of Auto (the default mode) or Relay may fail to connect to the relay service. A partial workaround may be to use Direct connection mode, however then guests must be on the same network as you in order to join the session. (Direct connections may also work through a VPN, depending on the VPN client and server configuration.) Please upvote and/or comment on this issue if you're experiencing proxy-related issues. Go to the Applications folder on your Mac’s hard drive, then go to the Utilities folder, and launch Disk Utility. • Select the drive you want to format. • Click the Erase button. Format mac usb on windows. • Click the Format menu, then choose either MS-DOS (FAT) or ExFAT. Warning: the following steps will delete any info you currently have on the drive. ![]() ![]() @kendruff The good news is we're past the SSL issue, the bad news is it sounds like you may have some needed locations blocked by your local or corporate firewalls - least when not going through the proxy. Try running these commands from a terminal (you can also grab ): curl curl then. Curl --noproxy '*' curl --noproxy '*' If the first two give you a 'document moved' HTML snippet while the last two cannot reach the destination, you're now hitting the proxy problem we have not resolved yet. Am I correct in assuming that is the case? As an aside, there was a circumstance where GitHub accounts were unable to start sharing (see ) but this should be resolved. This error is prior to that point so it likely is not related. I suspect there is also proxy issue when installing. I get stuck with this for about a minute: Followed by: curl curl outputs HTML curl --noproxy '*' curl --noproxy '*' outputs curl: (7) Failed to connect to download.visualstudio.microsoft.com port 443: Timed out At this point I don't see Live Share: Export Logs in the command palate. I'm able to install other extensions with no issue. Thanks for the awesome data. Follow these steps to set up your Internet connection if you’re using a network, cable modem, or DSL connection: Click the System Preferences icon in the Dock and choose Network. Select Ethernet from the list on the left of the pane to display the settings that you see here. Feb 16, 2016 - Using the secure settings in the Mac Mail client often leads to issues. Server account for InMotion Hosting, make sure that your mail server has. You are indeed correct. We cover this in, but here's the breakdown: • Finishing the installation (as you see above) for VS Code requires access to download.visualstudio.microsoft.com and download.microsoft.com • Signing in requires access to *.liveshare.vsengsaas.visualstudio.com (specifically insiders.liveshare.vsengsaas.visualstudio.com right now) • Running in 'relay' mode requires access to *.servicebus.windows.net Each of these may be impacted by this proxy issue depending on the exact rules your company has setup. I just checked and I get the same response from my cell phone so is there a server issue right now? Or is that an expected response? Here are my logs λ curl -k --noproxy '*' Document Moved Object MovedThis document may be found here λ curl -k --noproxy '*' 500 - Internal Server Error 500 - Internal Server Error Without the '-k' I get a self-signed error. Anybizsoft pdf to excel for mac. Is there a way to import my root cert? Does Live Share use a standalone cert store like curl/Firefox or the OS store as Chrome/IE/Windows? Curl: (60) SSL certificate problem: self signed certificate in certificate chain More details here: The Live Share error I get is [VSIX I] Acquired an access token for the VSO account ' [VSIX E] Failed to sign-in with the user ' credentials: Value cannot be null. Parameter name: loginTokenOrCode [VSIX E] Failed to create a collaboration session. Value cannot be null. Best vpns for mac. I'll be working with our network team on this too but they typically prefer to inject our corporate cert over opening up direct access. .NET doesn't yet provide support for proxy servers with https scheme, we only connect to proxies with http. Although note that you can access any http/https site through a proxy, the connection between the proxy and the site will be a tls channel in case of https, just that there's no tls connection between you and the proxy. This is the case with many browsers as well, supporting https proxies is not widely adopted yet.
0 Comments
Leave a Reply. |