Open PlayAnyData opened 2 years ago
That is an interesting one
the stack trace points to the http and netwrok error handling code. It may not be handling lower level network connection issues; The exact line seems to be where we pull http status objects out of responses this might happen if network errors prevent us for getting response objects.
Is your network access in WSL2 setup correctly? Are you able to successfully wget https://login.microsoftonline.com
?
Yes, this is working fine:
wget https://login.microsoftonline.com --2021-11-22 06:04:05-- https://login.microsoftonline.com/ Resolving login.microsoftonline.com (login.microsoftonline.com)... 20.190.159.134, 40.126.31.135, 40.126.31.137, ... Connecting to login.microsoftonline.com (login.microsoftonline.com)|20.190.159.134|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://www.office.com/login# [following] --2021-11-22 06:04:05-- https://www.office.com/login Resolving www.office.com (www.office.com)... 13.107.6.156, 2620:1ec:a92::156 Connecting to www.office.com (www.office.com)|13.107.6.156|:443... connected. HTTP request sent, awaiting response... 302 Found (...) HTTP request sent, awaiting response... 200 OK Length: 193728 (189K) [text/html] Saving to: ‘index.html’
I was having a very similar issue. In my case the problem was DNS resolution from within WSL2. Changing nameserver to a public DNS server like 8.8.8.8 did the trick for me. Here's a reference how to edit DNS settings on WSL2: https://gist.github.com/coltenkrauter/608cfe02319ce60facd76373249b8ca6
I had the same issue and changing the DNS server in WSL2 fixed it for me. Weird issue if you ask me
I am trying to create a workspace using:
Executing terraform apply the application crashes with the following exception:
Update: This happened to me within WSL2 (Ubuntu) on windows. However, on windows the same configuration works fine. I would prefer using Ubuntu.