Containerd registry configuration is not honored for initial bootstrap

Please run microk8s inspect and attach the generated tarball to this issue.
inspection-report-20210626_132458.tar.gz
For the initial microk8s node bootstrapping, any change made to use a private registry as  a docker.io or grc.io alternative is not used.

i haven't tried this, but your mirror is pointing to gcr.io, can you try using k8s.gcr.io?

Hi, it make no difference, still goes for the real mirror.

I looked at the containerd logs again.  I saw these errors.
Jun 26 13:09:32 rke-dmz7.cdf.jovenclub.cu microk8s.daemon-containerd[6962]: time="2021-06-26T13:09:32.229264502-04:00" level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:calico-node-b79v8,Uid:b4a02051-ec7f-44d9-8913-e39f6c4ea372,Namespace:kube-system,Attempt:0,} failed, error" error="failed to get sandbox image \"k8s.gcr.io/pause:3.1\": failed to pull image \"k8s.gcr.io/pause:3.1\": failed to pull and unpack image \"k8s.gcr.io/pause:3.1\": failed to resolve reference \"k8s.gcr.io/pause:3.1\": unexpected status code [manifests 3.1]: 403 Forbidden"
. . . .
  Coz its returning 403 Forbidden

No proxy is set. docker and gcr is restricted for a few countries including mine. We use a sonatype nexus as a local registry, this nexus goes over the TOR network in order to by pass this restrictions and save bandwith, the 403 is docker.io or grc.io doing what is set to do when is reached directly from my ISP's public ip. This use case is similiar to an airgap, but more efficient.

Lets try changing the location of the pause container.
In the file containerd-template.toml, can you try pointing it to your nexus?

Ok, so it seems that is the problem somehow,
microk8s kubectl describe  pod calico-node-cvxhh -n kube-system
 Normal   Pulling                 3m55s                 kubelet  Pulling image "calico/cni:v3.13.2"
  Normal   Pulled                  3m33s                 kubelet  Successfully pulled image "calico/cni:v3.13.2" in 22.064146951s
  Normal   Created                 3m32s                 kubelet  Created container upgrade-ipam
  Normal   Started                 3m32s                 kubelet  Started container upgrade-ipam
  Normal   Pulled                  3m30s                 kubelet  Container image "calico/cni:v3.13.2" already present on machine
  Normal   Created                 3m30s                 kubelet  Created container install-cni
  Normal   Started                 3m29s                 kubelet  Started container install-cni
  Normal   Pulling                 3m24s                 kubelet  Pulling image "calico/pod2daemon-flexvol:v3.13.2"
  Normal   Pulled                  3m14s                 kubelet  Successfully pulled image "calico/pod2daemon-flexvol:v3.13.2" in 10.778568842s
  Normal   Created                 3m11s                 kubelet  Created container flexvol-driver
  Normal   Started                 3m11s                 kubelet  Started container flexvol-driver
  Normal   Pulling                 3m10s                 kubelet  Pulling image "calico/node:v3.13.2"
  Normal   Pulled                  2m47s                 kubelet  Successfully pulled image "calico/node:v3.13.2" in 22.94440086s
  Normal   Created                 2m46s                 kubelet  Created container calico-node
  Normal   Started                 2m46s                 kubelet  Started container calico-node

microk8s kubectl get nodes NAME                          STATUS   ROLES    AGE   VERSION dtrccrpc01.ccr.jovenclub.cu   Ready    <none>   20d   v1.20.7-34+984a1cd176537e


Can not connect to internet in WSL 2

This happen on almost all official WSL distros (suse, debian, ubuntu) . I have not tried kali yet but i think the result will be the same.
This is the report on ubuntu:

Windows build number:  10.0.18932.1000

What you're doing and what's happening:

try to run sudo apt-get update

What's wrong / what should be happening instead:

Error message:

Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done

This seem like a dns issue, this is the content of my resolv.conf:

# This file was automatically generated by WSL. To stop automatic generation of this file, add the   following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
nameserver <IP_ADDRESS>

Run ipconfig from cmd and overwrite resolv.conf with the dns I get from ipconfig. Run apt-get update again. Host name can be resolved now, but get another error:

Err:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1560:8001::11). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1562::19). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1360:8001::17). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1360:8001::21). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2001:67c:1560:8001::14). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:80 (<IP_ADDRESS>), connection timed out Could not connect to security.ubuntu.com:80 (<IP_ADDRESS>), connection timed out Could not connect to security.ubuntu.com:80 (<IP_ADDRESS>), connection timed out Could not connect to security.ubuntu.com:80 (<IP_ADDRESS>), connection timed out Could not connect to security.ubuntu.com:80 (<IP_ADDRESS>), connection timed out Could not connect to security.ubuntu.com:80 (<IP_ADDRESS>), connection timed out
....

Try disable firewall, still the same error. I only use window defender, no other antivirus.

I convert my distro back to WSL 1 and every network command work fine. The content of resolv.conf in WSL 1 is surprisingly the same as when I overwrite the one in WSL 2

Expected: commands that require internet work as WSL 1

Strace of the failing command, if applicable:  can't, strace has not been installed yet beacause no internet. (I run strace on debian and got the command not found error, so I think ubuntu doesn't have them pre installed too). The log is quite long (3k+ lines) so I put them in a file:
apt-strace.log

I have a similar issue. Strangely it worked when I first convert to WSL2, but no longer works after a reboot.
For me, the windows hosts generates a WSL ethernet card:
    IP: <IP_ADDRESS>
    Mask: <IP_ADDRESS>

For the WSL ubuntu, ifconfig shows this:
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
    inet6 fe80::215:5dff:fe2e:c311  prefixlen 64  scopeid 0x20<link>
    ether 00:15:5d:2e:c3:11  txqueuelen 1000  (Ethernet)
    RX packets 379  bytes 37421 (37.4 KB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 13  bytes 1006 (1.0 KB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

when I try to use ping <IP_ADDRESS>, it comes back with connect: Network is unreachable.
I feel the problem is with the netmask, but not sure how to deal with it given the DHCP.

i also have this issue.When i convert the Ubuntu to wsl version 1, it can connect the Internet.
So i config the wsl vEthernet card,make it in the same netmask and reboot, but it doesn't work.Now i have removed the vethernet card, and i found it didn't be crearted any more...

try ifconfig down and up

I'm having this issue too.

I think the problem is because I had another virtual machine in Hyper-V (Docker For Windows), and there was another network adapter with the name br-25ddfb4f166c and eth0 with the wrong ip.
I uninstalled Docker For Windows and restarted the LxssManager (net stop LxssManager) service, and now the adapter is working normally.
It may be some conflict with adapters from other virtual machines.

The problem happened again. Restarting LxssManager does not resolve.

Is it possible to inspect WSL2 virtual machine settings? Its not visible in hyper-v console.

It is not a traditional VM so no. You can see it via hcsdiag.exe and container powershell apis though.

I had just to uninstall Docker for Windows, restart and the internet started working again in WSL 2! Note that I've uninstalled all virtualization applications last week, except for Hyper-V.

I had the same issue too. network unreachable, and nothing can connect.
The following resolved my issues:
# ifconfig eth0 netmask <IP_ADDRESS>                                                                                # ip route add default via <IP_ADDRESS>

Explanation:
I noticed that my $ ip addr didn't quite match my \>ipconfig:
$ ip addr show eth0
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:15:5d:db:c0:c6 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::215:5dff:fedb:c0c6/64 scope link tentative
       valid_lft forever preferred_lft forever

versus
 ipconfig                                                                                Windows IP Configuration

Ethernet adapter vEthernet (WSL):

   Connection-specific DNS Suffix  .  :

Virtual ethernet has subnet mask <IP_ADDRESS>.
So the first line changes it to the correct subnet mask.
# ifconfig eth0 netmask <IP_ADDRESS>

The second one simply adds <IP_ADDRESS> as the default gateway for all routes:
# ip route add default via <IP_ADDRESS>

I don't know if this is the 100% correct approach, but it certainly fixes this issue for me.

It is not a traditional VM so no. You can see it via hcsdiag.exe and container powershell apis though.

Thanks for the info.  Anecdotally, it does feel like its related to docker networking.
I seem to have found an acceptable workaround.  At login, it takes a while for docker to fully initialize.  With that, I added a WSL2 process that uses networking at startup which finishes before docker is initialized.  Specifically I'm exporting DISPLAY and loading an X window.
Working so far.

@samscott89 ip route add default via give me a RTNETLINK answers: File exists . How can I make it work?

@samscott89 ip route add default via give me a RTNETLINK answers: File exists . How can I make it work?

You might be fine without the second step then. After applying that step, I see:
$ ip route                                                                                default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/20 dev eth0  proto kernel  scope link  src <IP_ADDRESS>

Where <IP_ADDRESS> should match whatever ipconfig showed as the WSL ip address.
You will probably need (at least) both lines. If the first line is already there, then either you are good to go, or the issue is elsewhere

@samscott89  the ip address is match with ip in ipconfig but I still cannot ping or use curl. Hope MS address this issue asap because it is a blocker issue that prevent many user try and test WSL

What's the output of ipconfig (from cmd), and ip a and ip route on WSL?

ipconfig :
Ethernet adapter vEthernet (WSL):

   Connection-specific DNS Suffix  .   : No
   Autoconfiguration Enabled . . . .   Hope MS address this issue asap because it is a blocker issue that prevent many user try and test WSL 2

But yeah, fully agree. It seems I might have lucked out that my problem was actually fixable. There are a ton of related networking problems this build.

@Fubuchi The subnet mask looks wrong on yours as well. Should be /20, not /16. But I would expect it to work anyway.

There is another problem I am experiencing in WSL, I do not know if it has any relation to this problem but my downloads often stop.

Good call on the subnet mask, I'll get that fixed.

Steps From @samscott89

Open CMD.exe (windows not wsl) run ipconfig
Copy   'Subnet Mask'
Goto wsl and run sudo ifconfig eth0 netmask 'Subnet Mask'
4 Goto cmd and copy ' IPv4 Address'
Goto wsl and run sudo ip route add default via ' IPv4 Address'

For the record, this is now fixed for me on build 18932.

I have a similar issue. Strangely it worked when I first convert to WSL2, but no longer works after a reboot.
For me, the windows hosts generates a WSL ethernet card:
    IP: <IP_ADDRESS>
    Mask: <IP_ADDRESS>

For the WSL ubuntu, ifconfig shows this:
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
    inet6 fe80::215:5dff:fe2e:c311  prefixlen 64  scopeid 0x20<link>
    ether 00:15:5d:2e:c3:11  txqueuelen 1000  (Ethernet)
    RX packets 379  bytes 37421 (37.4 KB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 13  bytes 1006 (1.0 KB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

when I try to use ping <IP_ADDRESS>, it comes back with connect: Network is unreachable.
I feel the problem is with the netmask, but not sure how to deal with it given the DHCP.

You are right, looks like this is a dupe of https://github.com/Microsoft/WSL/issues/3438
Try this:
$ sudo ifconfig eth0 netmask <IP_ADDRESS>
$ sudo ip route add default via <IP_ADDRESS>

Resolved by @pauloscardine 's answer. Thanks.
But anyone figured out why it SUDDENLY happens? 🤔

I have a similar issue. Strangely it worked when I first convert to WSL2, but no longer works after a reboot.
For me, the windows hosts generates a WSL ethernet card:
    IP: <IP_ADDRESS>
    Mask: <IP_ADDRESS>

For the WSL ubuntu, ifconfig shows this:
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
    inet6 fe80::215:5dff:fe2e:c311  prefixlen 64  scopeid 0x20<link>
    ether 00:15:5d:2e:c3:11  txqueuelen 1000  (Ethernet)
    RX packets 379  bytes 37421 (37.4 KB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 13  bytes 1006 (1.0 KB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

when I try to use ping <IP_ADDRESS>, it comes back with connect: Network is unreachable.
I feel the problem is with the netmask, but not sure how to deal with it given the DHCP.

You are right, looks like this is a dupe of #3438
Try this:
$ sudo ifconfig eth0 netmask <IP_ADDRESS>
$ sudo ip route add default via <IP_ADDRESS>

Where <IP_ADDRESS> and <IP_ADDRESS> are the IP and netmask you got on the WSL interface (run ipconfig on windows and look for the WSL entry).

this fixes the issue for me but i have to do that every time i started wsl VM.
is the real fix coming soon?

ah, i just updated to insider 18963. the issue seems to be fixed in this build.

Confirmed, it was fixed in the latest insider build.

I'm on 18963 and just ran into this issue, got it working with @samscott89's approach.

I'm on 18963 and just ran into this issue, got it working with @samscott89's approach.

i'm on 18963 and wsl2 and the issue is fixed. are you using wsl1 by any chance?

I got same issue on 18963.1000, WSL2. And @samscott89's approach works properly.
If you don't have ifconfig command like me, use below commands:
# ip addr  # check if the current address is unmatched
# ip addr del <IP_ADDRESS>/24 dev eth0  # unmatched address of eth0
# ip addr add <IP_ADDRESS>/20 dev eth0  # new matched address
# ip route add default via <IP_ADDRESS>  # address of WSL2 adapter on Windows

Having the same issue on Build 18965

I think there was a regression. 18965 exhibits this issue with a WSL2 instance (openSUSE).

Having issues,<PHONE_NUMBER> Ubuntu

Because there are some people have this bug in Build 18965 , I will reopen it again.

I'm having the same bug, it's usually fixable issuing these on cmd:
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns

However, it seems to re-appear sometimes. I hope it gets fixed soon

@faustot please try to issue the commands you see above and restart your system

@leofabri I tried issuing the commands and rebooting, but it didn't resolve the network issue on my machine.

Seeing the same thing here on<PHONE_NUMBER>. The only way to "permanently" fix is to revert back to WSL1 for now.

If you're seeing this error could you help us by taking some networking logs when you're trying to access the internet?
Instructions on how to do so are here. Thanks!

feedback submitted

If you're seeing this error could you help us by taking some networking logs when you're trying to access the internet?
Instructions on how to do so are here. Thanks!

the same here in 18975 - always start with wrong ip address

I am on 10.0.18970.1005 and I had to do following 3 steps to solve this problem.

Set correct subnet mask
sudo ifconfig eth0 netmask <IP_ADDRESS>
Set default gateway
sudo ip route add default via <IP_ADDRESS>
Change DNS entry in  /etc/resolv.conf with <IP_ADDRESS>

In my case, I simply edited the /etc/resolve.conf and added my own dns entries and removed the one generated by the vm or whatever.

Typically /etc/resolv.conf is a symlink to a tmpfs location. In order for the /etc/wsl.conf setting to work, you'll also need to replace the symlink with a regular file.

Today i converted from WSL 1 to WSL 2
I didnt change from /etc/resolv.conf
I tried disable firewall from Avast Premium Security
and then i can update my ubuntu
But how connect to internet use firewall (Avast)?

Same sort of problem on 18990.
My subnet mask and IP route are set correctly automatically.
`Ethernet adapter vEthernet (WSL):
Connection-specific DNS Suffix  .
PING google.com (<IP_ADDRESS>) 56(84) bytes of data. ^C --- google.com ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4167ms

Hi guys,
I have the same problem, but I have fixed IP addresses on the interface that is connected to the internet.
So, first I remove the fixed IP addresses on the windows gui (dhcp enabled) and it worked.
Then, I put again my IP addresses and gateway.

Trying to convert back to WSL 1 aborts with an error about network connectivity.
C:\Users\ebert>wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Running         2

C:\Users\ebert>wsl --set-version Ubuntu 1
Conversion in progress, this may take a few minutes...
The network connection was aborted by the local system.

C:\Users\ebert>wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Stopped         2

Fix DNS resolution in WSL2
This fixed it for me.

Experiencing this as well. No idea what's causing it.

I figured the root cause was because I was blocking the incoming traffic in the "Public network" firewall

I've come to the same conclusion as Hoang when I activated firewall logging
and monitored the output using cmtrace.
On Mon., Nov. 4, 2019, 11:25 p.m. Hoang Nguyen<EMAIL_ADDRESS>wrote:

I figured the root cause was because I was blocking the incoming traffic
in the "Public network" firewall
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/WSL/issues/4275?email_source=notifications&email_token=AFAAF72X5B3IFZMDSAIU44DQSDYSFA5CNFSM4H6SKCKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDBRWDA#issuecomment-549657356,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFAAF7ZJOOPXCZLDRJVNAXTQSDYSFANCNFSM4H6SKCKA
.

Same! Firewall had to be disabled. This was not needed in WSL1. I hope this will be fixed in future versions.

Just open the specific port it requires, don't let everything open ;)
Eric
On Mon., Nov. 18, 2019, 7:38 a.m. Abhirup Das<EMAIL_ADDRESS>wrote:

Same! Firewall had to be disabled. This was not needed in WSL1. I hope
this will be fixed in future versions.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/WSL/issues/4275?email_source=notifications&email_token=AFAAF7YXKZCIYYW4XHYSPW3QUKEEHA5CNFSM4H6SKCKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEKJRIY#issuecomment-554997923,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFAAF72VEEVKPMAGH3PPY5LQUKEEHANCNFSM4H6SKCKA
.

I had this problem after installing WSL2. I had docker desktop running when I installed it. I uninstalled docker desktop, that did not fix it for me yet. I tried turning off the firewall. that did not work.
Then I went to the advanced settings in the Ubuntu distro app and clicked the reset button to re-install WSL2. Now it works.

I had this problem after installing WSL2. I had docker desktop running when I installed it. I uninstalled docker desktop, that did not fix it for me yet. I tried turning off the firewall. that did not work.
Then I went to the advanced settings in the Ubuntu distro app and clicked the reset button to re-install WSL2. Now it works.
EDIT:
I thought it was working after the reinstall, but I forgot to set the Ubuntu-18..04 distro to version wsl2, so it was working as wsl1. After converting to wsl2, internet stop working.
I installed wsl2 on my work laptop and everything works, which is a very similar set up to my home laptop.

Try modifying /etc/resolv.conf to Google's DNS.
nameserver <IP_ADDRESS>

@agarciamog I have now tried all the suggestions in this thread and another open thread and still can't get it to work.
I have added google's DNS to resolv.conf, this is the error I am currently getting (I've trimmed the repeatition, and it was different before but can't reproduce the first error anymore).
$ sudo apt-get update
  Temporary failure resolving 'security.ubuntu.com'
Err:2 http://archive.ubuntu.com/ubuntu bionic InRelease
  Temporary failure resolving 'archive.ubuntu.com'

Reading package lists... Done
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease  Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease  Temporary failure resolving 'archive.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.```

`$ ip addr | grep eth0`
```4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    inet <IP_ADDRESS>/20 brd <IP_ADDRESS> scope global eth0```

Windows terminal `ipconfig`

Ethernet adapter vEthernet (WSL):
Connection-specific DNS Suffix  .  It seems like the problem is DNS resolving. My home PC is WIFI only, that could have something to do with the problem.
I've moved my comments over to this issue as that looks like the exact problem I have.
Thanks for the suggestions.

hi @rm-bergmann
Try this https://gist.github.com/coltenkrauter/608cfe02319ce60facd76373249b8ca6
Thats work for me, but still must disable my firewall

Hi @dzhenway
Thank you.

Error after I get when using google's nameserver:
Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
  Temporary failure resolving 'archive.ubuntu.com'

$ ping google.com
> ping: google.com: Temporary failure in name resolution

$ ping <IP_ADDRESS>
> PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.

I'm out of things to try now but I'll update if I find a solution.
Thanks.

For me at least, this is definitely not a DNS resolution issue.  I can't ping any IP address directly, including addresses on a local network. I can ping the WSL ethernet interface, but nothing beyond it (not even the host machine's IP).
This works fine on my desktop, but not my laptop.  The only relevant thing I can think that could be different is that the laptop has wifi + ethernet (and I switch often between them - dock/undock), but the desktop has only ethernet.

I have now tested the WIFI vs Ethernet on both my home PC and office PC.
Office PC is on Ethernet, WSL2 works well. I unplugged the ethernet and connected to WIFI and ran sudo apt update in WSL2. It connected fine and I updated and upgraded packages successfully on WIFI.
Home PC is on WIFI. I disconnected WIFI and plugged in an ethernet from the router, checked Internet was working and ran sudo apt update and I got the Temporary failure resolving 'archive.ubuntu.com' error message.
I still have no luck finding a solution.

I have the same problem today. It worked well yesterday, I have no idea what I did.

For the record, this is now fixed for me on build 18932.

But the problem returned on 19037 and the previous solution doesn't work

Just update to 19041, problem solved.

and 19041.1 has the same problem , the previous solution doesn't work too.

and i' trying to upgrade to insider preview 19536.1000,  may be the newer version of windows 10 could resolve this problem.

19041 seemed to solve the problem until the first reboot. The only solution
for me was to include the WSL mac address into Norton firewall trusted
devices and restarting WSL.
Ciro
Em qui, 12 de dez de 2019 00:14, Domain<EMAIL_ADDRESS>escreveu:

Just update to 19041, problem solved.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/WSL/issues/4275?email_source=notifications&email_token=AABM7YMP73R3E76PK73DQ3TQYGM6TA5CNFSM4H6SKCKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGVHGCQ#issuecomment-564818698,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABM7YKMU45OQQPOOIH4ANDQYGM6TANCNFSM4H6SKCKA
.

i was upgrad to 19536.1000, but still not working.
and  i also reboot multi times.

Does it work when you ping your Windows host WSL ip address from a WSL2 shell?
Here it says that connection failed to my enterprise firewall (on Windows host) that listens on <IP_ADDRESS>...
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease  Connection failed [IP: <IP_ADDRESS> 9000]
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease  Connection failed [IP: <IP_ADDRESS> 9000]
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease  Connection failed [IP: <IP_ADDRESS> 9000]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease  Connection failed [IP: <IP_ADDRESS> 9000]

It only worked one time when I upgraded to 19541.1000...
Also, @craigloewen-msft, it didn't work to record a diagnostic log using the feedback tool. It said that it can't start the capture... :(

The following fixed my problem:
Upon examining the contents of /etc/resolv.conf, I discovered the file seemed to have been overwritten or corrupted. It contained nothing but a single line of
#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#<EMAIL_ADDRESS>Using sudo, I overwrote the contents of the file with the following:
# This file was automatically generated by WSL. To stop automatic generation of this file, remove this line. nameserver <IP_ADDRESS> nameserver <IP_ADDRESS>
Saved, restarted WSL, and it worked like a charm.

(Build 19041)
For full disclosure, I do have Docker daemon installed inside WSL, however it was not running at the time that this error was experienced.
I was experiencing a similar network-adapter related issue after the first reboot following initial WSL2 installation, but it didn't seem to be a configuration fault. Netmasks, gateways, and routes all seemed to be correct on the guest and host. However I noticed that the WSL Adapter on the Host reported its IPv4 address as "Duplicate," i.e., experiencing an IP conflict:
Ethernet adapter vEthernet (WSL):

   Connection-specific DNS Suffix  .   : No
   Autoconfiguration Enabled . . . .   : Enabled

There were no other interfaces using this IP on the host that I could see, so the detection as a duplicate seems to be in error..
I disabled and re-enabled this interface in the Network and Sharing Center, and now the "(Duplicate)" label is gone despite having the same IPv4 address. Last step after resolving the conflict was to restart wsl with wsl --terminate [distro], and now I have networking restored. Don't yet know if this is a permanent fix.

This issue was resolved on my machine by uninstalling the CheckPoint VPN client.
Microsoft Windows [Version 10.0.19041.84]

i use a lot on a daily basis in vmware IT modules and testing load balancers in front certain open source firewall monitoring tools.
i can tell you from my experience that without proper planing and being careful its very easy to block vast amount of important incoming communication. i had my fair share of that mistakes.
if some of you are working in parallel project with virtual modules i suggest two things:
1.decrease the number of virtual adapter as much as you can.
manipulate main setting and expand them in the module and not the production.
2.use opensource net/routs for your advantage.
3.increase the use of platform based load balancers.
4.virtual adapters aren't so friendly to wsl.
most people tend to forget that virtual networks aren't classic protocols  but more application protocol.so naturaly there would be collisions.
disabling most virtual networks temporarily always solved my problem.
this way you can leave your network clean and optimized for incoming connections.

This issue was resolved on my machine by uninstalling the CheckPoint VPN client.
Microsoft Windows [Version 10.0.19041.84]

I likewise had interference caused by CheckPoint VPN. Uninstalling it fixed my issue. Now I need to put it on a VM

I Disabled avast firewall and everything worked.

@Laynkulan @Rogn I can't uninstall CheckPoint VPN or disable Avast since this is a company machine.
Do you want what the problem is, so I can direct the IT?

I experienced this issue using WSL2, Windows build 19041.208.
I tried:

I attempted to see the netmask/ip route default as described above
Disabled the Firewall
Restarted the WSL VM

Finally, I restarted Windows and that resolved it.

Still getting this issue.

internet not working in wsl2, but wsl1 is working fine for all distros, I thought I messed up something, completely reinstalled windows, but the problem exists.

nothing in the above seems t be working my default ip route exist

I got the same error when using Citrix VPN client in WSL 2 (windows build 19041.208)

I've installed ubuntu 20.04 on WSL2 and I started a VM with qemu and kvm,running mac os x as guest os. It works great,except for the configuration of the net. Infact it is not able to connect to internet. Sometime from WSL I get a 192.x.x.x ip number,like :
<IP_ADDRESS> ; <IP_ADDRESS> ; <IP_ADDRESS> ; <IP_ADDRESS> ; <IP_ADDRESS>
sometime I get a 172.x.x.x ip address,like : <IP_ADDRESS> ; <IP_ADDRESS> ; <IP_ADDRESS> ; <IP_ADDRESS>.
The vEthernet (WSL) adapter on Windows 10 is configued like this : <IP_ADDRESS> as IP address,subnet mask = <IP_ADDRESS>
I have created a bridge in WIndows 10,between my Intel ethernet adapter and the tap0 / Tap-windows. It's IP is <IP_ADDRESS> ; subnet mask = <IP_ADDRESS> ; gateway = <IP_ADDRESS> ; dns primary = <IP_ADDRESS>
I have configured WSL like it is explained,but it didn't work. Check below what happens :
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# brctl addbr br0
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# ip addr flush dev eth0
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# brctl addif br0 eth0
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# tunctl -t tap0 -u root
Set 'tap0' persistent and owned by uid 0
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# brctl addif br0 tap0
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# ifconfig eth0 up
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# ifconfig tap0 up
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# ifconfig br0 up
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.00155d99cfa4 no eth0
tap0
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# dhclient -v br0
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/br0/00:15:5d:99:cf:a4
Sending on LPF/br0/00:15:5d:99:cf:a4
Sending on Socket/fallback
DHCPDISCOVER on br0 to <IP_ADDRESS> port 67 interval 3 (xid=0xbbd3b615)
DHCPDISCOVER on br0 to <IP_ADDRESS> port 67 interval 8 (xid=0xbbd3b615)
DHCPDISCOVER on br0 to <IP_ADDRESS> port 67 interval 12 (xid=0xbbd3b615)
DHCPDISCOVER on br0 to <IP_ADDRESS> port 67 interval 11 (xid=0xbbd3b615)
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::215:5dff:fe99:cfa4 prefixlen 64 scopeid 0x20
ether 00:15:5d:99:cf:a4 txqueuelen 1000 (Ethernet)
RX packets 172 bytes 43127 (43.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 16 bytes 2304 (2.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 00:15:5d:99:cf:a4 txqueuelen 1000 (Ethernet)
RX packets 543 bytes 121055 (121.0 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 28 bytes 3280 (3.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet <IP_ADDRESS> netmask <IP_ADDRESS>
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tap0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 46:88:cb:85:5f:9e txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@DESKTOP-N9UN2H3:/mnt/c/Android/sdk/platform-tools# ping www.google.it
ping: www.google.it: Name or service not known
I think IPv4 issue can be solved with configuring DHCP, but I don't know how to do that. I dont know why after removing address from eth0, which had an ipv4 address, and creating a bridge,it becomes no ipv4.

Same issue with PulseSecure VPN

It was NordVPN for me, uninstalled. Works fine.

The following fixed my problem:
Upon examining the contents of /etc/resolv.conf, I discovered the file seemed to have been overwritten or corrupted. It contained nothing but a single line of
#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#<EMAIL_ADDRESS>Using sudo, I overwrote the contents of the file with the following:
# This file was automatically generated by WSL. To stop automatic generation of this file, remove this line.
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
Saved, restarted WSL, and it worked like a charm.

Worked for me. Before WSL crashed a few times when deleting huge folders (node_modules). Maybe thats what corrupted that file.

I don't have the same issues as above.
For me the issue is likely that I have no DNS server configured on my VirtualSwitch gateway
$ ip a
[snip]
5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:15:5d:46:38:3d brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/20 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::215:5dff:fe46:383d/64 scope link
       valid_lft forever preferred_lft forever
$ ip route
default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/20 dev eth0 proto kernel scope link src <IP_ADDRESS>

When I change my resolv.conf file with a public DNS server, it works.
I want WSL2.0 to use the DNS setup on my host. I could configure it statically but it can change depending on the network I am in.
Is anyone experiencing the same as me?
I am on 19041.264

My case it is unable to ping to any of the addresses from WSL 2 when I connect to VPN (Cisco Anyconnect VPN client). I am running Windows 10 Enterprise Version 2004 (OS Build 19041.264)
It did work after conversion from WSL1 to 2 and before reboot.  As i could see the default route is to reach the gateway on the host, that itself failed. Hence it is the main reason for failure.
Tried multiple things and ended up uninstalling WSL2. Afterwards I faced no issues with WSL1. When i checked the difference WSL1 is using windows routes instead of bridging with a dedicated host interface.
I think MS screwed the routing with VPN enabled!

It is not a traditional VM so no. You can see it via hcsdiag.exe and container powershell apis though.

Thanks for the info. Anecdotally, it does feel like its related to docker networking.
I seem to have found an acceptable workaround. At login, it takes a while for docker to fully initialize. With that, I added a WSL2 process that uses networking at startup which finishes before docker is initialized. Specifically I'm exporting DISPLAY and loading an X window.
Working so far.

This indeed seems to be the case for me as well.
Windows 10 Pro, Build 19041.264
WSL 2, Running Ubuntu 20.04 from the Windows Store
Docker (Engine) version 19.03.8, build afacb8b
Docker Desktop version <IP_ADDRESS> (45408)
Even if I forget to do some networking-related stuff before starting Docker Desktop, I can still connect to the outside from within my docker containers. Just not from within my WSL2 distros...
Very odd indeed.

Hi,
I'm able to connect to the "web" in example via curl, using this
sudo bash -c 'echo "nameserver <IP_ADDRESS>" > /etc/resolv.conf'
sudo bash -c 'echo "nameserver <IP_ADDRESS>" >> /etc/resolv.conf'

But it's impossible to use python pip. How solve this issue?
Thank you

Hi,
I'm able to connect to the "web" in example via curl, using this
sudo bash -c 'echo "nameserver <IP_ADDRESS>" > /etc/resolv.conf'
sudo bash -c 'echo "nameserver <IP_ADDRESS>" >> /etc/resolv.conf'

But it's impossible to use python pip. How solve this issue?
Thank you

Solved writing again /etc/resolv.conf  :(

The following fixed my problem:
Upon examining the contents of /etc/resolv.conf, I discovered the file seemed to have been overwritten or corrupted. It contained nothing but a single line of
#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#@#<EMAIL_ADDRESS>Using sudo, I overwrote the contents of the file with the following:
# This file was automatically generated by WSL. To stop automatic generation of this file, remove this line.
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
Saved, restarted WSL, and it worked like a charm.

My file was corrupted but fixing it, didnt get my internet connectivity back. Before WSL crashed a few times when deleting huge folders (node_modules). Maybe thats what corrupted that file.
What helped was the following:
On cmd execute:
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns

in WSL:
sudo bash -c 'echo "nameserver <IP_ADDRESS>" > /etc/resolv.conf'
sudo bash -c 'echo "nameserver <IP_ADDRESS>" >> /etc/resolv.conf'

found in #3438

using
sudo bash -c 'echo "nameserver <IP_ADDRESS>" > /etc/resolv.conf'
sudo bash -c 'echo "nameserver <IP_ADDRESS>" >> /etc/resolv.conf'

after connecting my VPN worked perfectly!

@df3l0p I've experienced exactly the same behaviour. Networking didn't work only in WSL 2, after downgrading Ubuntu to WSL 1 the connectivity issue didn't persist. As @michidk suggested above - I have overwritten the DNS settings with a public DNS server by running
sudo bash -c 'echo "nameserver <IP_ADDRESS>" > /etc/resolv.conf'
sudo bash -c 'echo "nameserver <IP_ADDRESS>" >> /etc/resolv.conf'

which fixed the issue.
I've just upgraded Windows to version 2004 (OS Build 19041.264) today to test out the new WSL 2.
EDIT: the issue comes back after restart. To fix it permanently: https://gist.github.com/coltenkrauter/608cfe02319ce60facd76373249b8ca6
Note: originally /etc/resolv.conf was a symbolic link to /run/resolv/resolv.conf. Creating a resolv.conf file in /run/resolv didn't fix this issue as it got deleted after invoking wsl --shutdown and restarting Ubuntu. I had to sudo rm /etc/resolv.conf and recreate the file as the gist says.

Thank you, it works for me.

I created this because of the need to rerun it now for every new distro created ...
https://github.com/aaronlks/wsl2-19041-fixDNS/blob/master/fixdns.sh
hope this gets fixed upstream

I have been facing the same problem for the last day or so. In my case it turns out to be the firewall.
At the working laptop, we use Avast, for me to make it work again I had to enable Internet Connection Sharing mode on the Avast firewall settings.
I am reporting here because it may be of some help to someone else out there.

I have the same problem when I'm connected via the Citrix VPN client when my distro is in WSL 2 mode.
I'm running Windows build 19041.329.

i've got no internet access in a newly installed ubuntu subsystem.
also running 19041.329.
Should the IPs of the subsystem and the virtual adaptor on the host be on the same subnet? they're not in my case.

I met same issue on 19041.329 with ubuntu 20.04.
and none of the above workarounds work for me.

Seems like there are mutiple issues out there in regards to this "same issue".  I read through much of them and with the help of my IT department we came up with a solution I've stated at #4246 here.

So I just worked with my IT Department on coming up with a fix. Here's what we found out and how we corrected it.
When you connect to Cisco Anyconnect WSL2 will NAT to the highest priority Ethernet Adapter. A newer version of Cisco Anyconnect from the Windows Store seems to correct this; however, it doesn't support Dual Factor Authentication. So to correct this we used a script that I saw mentioned elsewhere.
Steps:
Restart Computer (or begin from fresh start)
Login to Computer, Connect via Cisco AnyConnect
Run a script from Powershell that includes the follow (Note: your adapter name may need to be changed on Line 2 in quotes)
Get-NetIPInterface -InterfaceAlias "vEthernet (WSL)" | Set-NetIPInterface -InterfaceMetric 1
$VPNInterfaceName = "Ethernet 3"
Get-NetIPInterface -InterfaceAlias $VPNInterfaceName | Set-NetIPInterface -InterfaceMetric 5001
Once that's been completed open WSL and you should be good to go, unless there is something else causing further issues that I had not experienced.
I hope this helps, as we spent several days attempting to track down the cause.
Edit: Be sure if you have "Ubunut/WSL" set as your default profile in Windows Terminal, that you run the script prior to starting WSL. So if Ubuntu/WSL is your default, set your default to PowerShell, or switch over to PowerShell, run the command wsl --shutdown, then execute the above script, then reopen Ubuntu/WSL.

I believe this is fixed with the latest builds and this issue can be closed.
My issue was my anti-virus firewall. I disabled it and WSL 2 network was working again. Now, I just need to figure out which exceptions to provide, so I can re-enable my firewall.
Windows Version

Windows WSL Version
>wsl -l -v
  NAME                   STATE           VERSION
* Ubuntu-20.04           Running         2
  docker-desktop         Running         2
  docker-desktop-data    Running         2

Docker Version (with WSL 2 integration and Kubernetes)

Steps From @samscott89

Open CMD.exe (windows not wsl) run ipconfig
Goto 'Ethernet adapter vEthernet (WSL):'
Copy   'Subnet Mask'
Goto wsl and run sudo ifconfig eth0 netmask 'Subnet Mask'
5 Goto cmd and copy ' IPv4 Address'
Goto wsl and run sudo ip route add default via ' IPv4 Address'

The biggest problem:
$ ipconfig

Command 'ipconfig' not found, did you mean:

  command 'iwconfig' from deb wireless-tools (30~pre9-13ubuntu1)
  command 'ifconfig' from deb net-tools (1.60+git20180626.aebd88e-1ubuntu1)
  command 'iconfig' from deb ipmiutil (3.1.5-1)

Try: sudo apt install <deb name>

Apart from adding routes and nameservers, Kapersky was causing the issue for me. Stoping it was not working either probably it was making changes to some system files to prevent access to WSL application. I found this to be helpful:
Go to: More Tools -> Manage Application -> Application Control -> Manage Application -> 'your WSL app name' -> click on network(green arrow) -> Change value to allow.
Attaching screen shot of same:

I don't know how to explain why this is yet but i'm searching for answers. When I connect my laptop to internet using Ethernet through USB-C (a docking station) unbuntu loses all internet connections. But if I disable the Ethernet connection it and it switch back to Wi-Fi the internet starts working for ubuntu.
I recently did this fix to get my port binding again but then this internet issue started happening...
https://github.com/docker/for-win/issues/3171#issuecomment-572571882

Steps From @samscott89

Open CMD.exe (windows not wsl) run ipconfig
Goto 'Ethernet adapter vEthernet (WSL):'
Copy   'Subnet Mask'
Goto wsl and run sudo ifconfig eth0 netmask 'Subnet Mask'
5 Goto cmd and copy ' IPv4 Address'
Goto wsl and run sudo ip route add default via ' IPv4 Address'

problem is there is no connectivity and ifconfig command not found in wsl.. what to do?

You probably forgot to add
nameserver 'IPv4 Address'
to your /etc/resolv.conf in wsl so you don't manage to resolve names to IPs
try to ping <IP_ADDRESS> and check if it works

Just to say that everything seems to be ok, but still no ethernet connectivity, only wifi, after wsl 2 install and normal usage.

Goto wsl and run sudo ifconfig eth0 netmask 'Subnet Mask'

ifconfig is a no-go on some builds until you're able to get internet access and install net-tools.

I don't know why but disabling Mobile Hotspot fixed it for me.

I'm having the same issue and can't figure out how to fix it. I'm on Windows 20211 dev build using the default Ubuntu release

Went through a bunch of solutions. Nothing worked. Found out the problem was my %temp% folder (C:\Users\username\AppData\Local\Temp) was compressed. I uncompressed it and that fixed it immediately.

Including nameserver <IP_ADDRESS> in my /etc/resolv.conf seemed to do the work.

for me the workaround of adding a custom nameserver has been working perfectly for the last couple of months. As of today, I no longer have internet either with or without that workaround. What's changed?
also, why is this ticket 'closed'? Given the number of people responding, it's pretty clear that there is not yet a clear solution or consistent workaround for the issue here.

What happened to my WSL2

It turned out to be working normally, but suddenly it was abnormal
Using a proxy works fine
DNS is working normally (use the host command to view)
win ping wsl ok
wsl ping win no response
ping baidu.com shows TTL=1
Restarting the computer does not work
Reinstalling WSL2 is invalid
Restoring network settings is invalid
The following is a screenshot of wireshark capture (wsl ping win)

Final solution
The network manager turned off the secondary router, and then the network manager turned on the secondary router and the wsl2 network worked normally.

我也一样, ipconfig一看 default switch 和 wsl 都是媒体已断开

Uninstalling Docker desktop worked for me. Not a good solution though.

using
sudo bash -c 'echo "nameserver <IP_ADDRESS>" > /etc/resolv.conf'
sudo bash -c 'echo "nameserver <IP_ADDRESS>" >> /etc/resolv.conf'
after connecting my VPN worked perfectly!

+1 for @erickucl solution.
I just had this problem today. This was the missing piece to solve it.
I'm commenting to underline that this is an ongoing issues.
Windows build: 18363.1139
Docker For windows: v19.03.13 (with WSL2 based engine)
Additional note: I'm using vscode with both WSL2 and docker. (maybe there's a link ?)

I would also like to add myself to the list of the lucky ones. Today I broke all my development environments by installing docker desktop. After removing and rebooting, my development environments work normally again, and I can connect to the internet again.

 Nothing worked. Found out the problem was my %temp% folder (C:\Users\username\AppData\Local\Temp) was compressed. I uncompressed it and that fixed it immediately.

This fixed my problem, thank you. I guess problem started after I compressed C drive.

Steps From @samscott89

Open CMD.exe (windows not wsl) run ipconfig
Goto 'Ethernet adapter vEthernet (WSL):'
Copy   'Subnet Mask'
Goto wsl and run sudo ifconfig eth0 netmask 'Subnet Mask'
5 Goto cmd and copy ' IPv4 Address'
Goto wsl and run sudo ip route add default via ' IPv4 Address'
When I run
sudo ifconfig eth0 netmask 'Subnet Mask'
I get this:
SIOCSIFNETMASK: Cannot assign requested address
Here is my Ethernet adapter vEthernet (WSL):

   Connection-specific DNS Suffix  .  :

Wait It just fixed it self I didn't do a thing

** By far the easiest solution that worked for me!
Turn off Fast Start-Up in the System Settings -> Shut-down Settings. Then reboot. That's it.
found the solution here...
https://stephenreescarter.net/wsl2-network-issues-and-win-10-fast-start-up/

For me this happens after change my PC internet, I was using Wi-Fi and now I'm using internet cable.
I think I solved this just uninstalling docker, restarting my pc and after that it was working again. So I reinstalled the docker and it was Ok.

https://github.com/microsoft/WSL/issues/3438#issuecomment-751186376
this one works for me

the only thing that worked form https://stackoverflow.com/a/54460886/4740149

the only thing that worked form https://stackoverflow.com/a/54460886/4740149

Version 1909 (OS Build 18363.1139), WSL 2

Nothing worked for me. I can not update Windows since this is a company laptop. I had to go back to WSL 1. I will ping back in a year or so when we get another update from our company IT :(

Version 1909 (OS Build 18363.1139), WSL 2

Nothing worked for me. I can not update Windows since this is a company laptop. I had to go back to WSL 1. I will ping back in a year or so when we get another update from our company IT :(

To elaborate on what's posted a few comments above, Windows Update KB4023057 introduced the possibility to file compression before updates when system is running on low storage.
That includes %Appdata% (Local, LocalLow, Roaming) and subsequently %Temp%, if the distro's files are compressed it won't initialize and if %Temp% is compressed, you won't have an internet connection.
To decompress folders (and files inside), right click on folder properties and under advanced uncheck all boxes related to allowing compression and reboot after.

To elaborate on what's posted a few comments above, Windows Update KB4023057 introduced the possibility to file compression before updates when system is running on low storage.
That includes %Appdata% (Local, LocalLow, Roaming) and subsequently %Temp%, if the distro's files are compressed it won't initialize and if %Temp% is compressed, you won't have an internet connection.
To decompress folders (and files inside), right click on folder properties and under advanced uncheck all boxes related to allowing compression and reboot after.

I don't know why but disabling Mobile Hotspot fixed it for me.

This works for me, too. But if I reboot my machine, everything is fine. I can access the network without any trouble even when
hotspot is enabled.

I don't know why but disabling Mobile Hotspot fixed it for me.

This works for me, too. But if I reboot my machine, everything is fine. I can access the network without any trouble even when
hotspot is enabled.

 Nothing worked. Found out the problem was my %temp% folder (C:\Users\username\AppData\Local\Temp) was compressed. I uncompressed it and that fixed it immediately.

This solved my issue as well, thanks!
Compression likely kicked in after a reboot with low disk space, and apparently that is causing all sorts of problems. Before I encountered the internet problem, I had to solve a similar issue that prevented WSL to start due to a compression of %USERPROFILE%\AppData\Local\Packages\CanonicalGroupLimited\LocalState, which prevented WSL to start. Link to that particular issue for reference.

I had just to uninstall Docker for Windows, restart and the internet started working again in WSL 2!
this worked for me too

I had just to uninstall Docker for Windows, restart and the internet started working again in WSL 2!

this worked for me too
after that I reinstalled docker again and it still worked afterwards

even though i restarted my pc yesterday a few times inbetween this, it's not working again today
a reinstall of docker might fix the issue for me again
but nevertheless this is an absolute nightmare to work with in this state

I had this problem after turning on Astrill VPN. Uninstalling it and rebooting my computer fixed my issue, but I don't know why

** By far the easiest solution that worked for me!
Turn off Fast Start-Up in the System Settings -> Shut-down Settings. Then reboot. That's it.
found the solution here...
https://stephenreescarter.net/wsl2-network-issues-and-win-10-fast-start-up/

This works for me! Thank you!

Hello all,
For me the issue was happening when I connected to my work's VPN a bit too fast in the morning
I was able to solve this by disconnecting to the VPN then restart LxssManager windows service and reconnect to the VPN again.
To restart this service you can do it from interface: search services, open, right click LxssManager in the service list and restart
Or by powershell as admin command line: Get-Service LxssManager | Restart-Service

In my case it was a DNS resolving issue. I edited my /etc/resolv.conf file deleted all existing lines and added only this one:
nameserver <IP_ADDRESS>

none of this helped but answer on stackoverflow helped
https://stackoverflow.com/a/64057835/1319799
wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns
netsh winsock reset
shutdown /r

none of this helped but answer on stackoverflow helped
https://stackoverflow.com/a/64057835/1319799
wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns
netsh winsock reset
shutdown /r

Thanks this works for me too. I'm facing connection issue after downloading github desktop for windows.

My case is a little bit different.
When I'm using desktop VPN (Tunn** Be**), I can't connect to the internet from WSL2 I realize it after turning off the VPN and tried to apt update. Could anyone know what's actually going on?

none of this helped but answer on stackoverflow helped
https://stackoverflow.com/a/64057835/1319799
wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns
netsh winsock reset
shutdown /r

That also worked for me.
Just wondering (need time to research) what's the effect of those steps. Some considerations:

didn't perform a windows reboot after installing the linux distro (ubuntu20)
right after installing the linux distro, DNS resolved fine, but no access to (i.e.) ubuntu repos.
(BTW, DNS is configured by default as the WSL gateway, should be the beforehand referred "IPv4 Address" from ipconfig's output >> that will refer the request to your Windows (acting as gateway) and then to your internet router and so on; if changed to <IP_ADDRESS> you're using google's DNS... in fact reaching the internet).
Docker desktop is installed, though never used it. Didn't reinstall or so

Curious if the final "shutdown /r" from stackoverflow was the one that did the trick, may never know.

wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns
netsh winsock reset
shutdown /r

This is worked for me

none of this helped but answer on stackoverflow helped
https://stackoverflow.com/a/64057835/1319799
wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns
netsh winsock reset
shutdown /r

That also worked for me.
Just wondering (need time to research) what's the effect of those steps. Some considerations:
1. didn't perform a windows reboot after installing the linux distro (ubuntu20)

2. right after installing the linux distro, DNS resolved fine, but no access to (i.e.) ubuntu repos.
   (BTW, DNS is configured by default as the WSL gateway, should be the beforehand referred "IPv4 Address" from ipconfig's output >> that will refer the request to your Windows (acting as gateway) and then to your internet router and so on; if changed to <IP_ADDRESS> you're using google's DNS... in fact reaching the internet).

3. Docker desktop is installed, though never used it. Didn't reinstall or so

Curious if the final "shutdown /r" from stackoverflow was the one that did the trick, may never know.
Thanks you. This is worked for me.

none of this helped but answer on stackoverflow helped
https://stackoverflow.com/a/64057835/1319799
wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns
netsh winsock reset
shutdown /r

This is worked for me

In my case it was a DNS resolving issue. I edited my /etc/resolv.conf file deleted all existing lines and added only this one:
nameserver <IP_ADDRESS>

Thanks, I tried everything without success until adding this nameserver :)

This feels hacky but it's working or me. I ran these commands from inside WSL
$ cat /etc/wsl.conf
[network]
generateResolvConf = true
nameserver=<IP_ADDRESS>

$ cat fix_resolve.sh
#!/bin/bash

sudo sed -i 's/nameserver.*/nameserver <IP_ADDRESS>/g' /etc/resolv.conf
cat /etc/resolv.conf

$ head -n 2 ~/.bashrc
bash /mnt/c/Users/kurtf/fix_resolve.sh
sudo ntpdate time.windows.com

Now, when I wsl--shutdown, it still works as bashrc in Ubunutu resets resolv.conf. When the laptop goes to sleep and I start the wsl shell, ntupdate runs and gets things back in sync.

In my case it was a DNS resolving issue. I edited my /etc/resolv.conf file deleted all existing lines and added all nameserver which is listed in IPv4 DNS Servers: (under network connection details)

The simple procedure that works is to modify the c:\users%USERPROFILE%.wslconfig file to be:
[wsl2]
memory=8GB
swapFile=0
swap=0
For some reason someone at microsoft changed the name of the swap config parameter.
Stragely, when swapfile is defined. network works like a whistle.
Microsoft: Please decouple swalfile from network. And consider supporting both names for the swap.

Hi,
I had the same issue ... i was reading similar issues in many forums.
I am using Windows 10.
This is the solution that worked for me:

First check your ethernet connection for WSL

Check out the network status for vEthernet (WSL )

For me initially the received was 0 or some low values like 1 or 2 .
TO fix this we have to :

Open Hyper V Manager > Virtual Switch Manager
Select WSL and set the Network to External and choose the appropriate Network adapter that is connected to internet

If your are good till now, you should see sent and received packets going up. Like the one in step 2.
(When i checked out the connection properties > Ip V4 : Ip address and DNS was set to configure automatically)

Remaining fix have to be done in your Linux env. I have Ubuntu 20.04 installed.

Open Ubuntu 20.04

set the network ip address and netmask:  sudo ifconfig eth0 <ip_address> netmask <net_mask>
This ip_address should be same as the IP address you got for WSL Adapter. You can see these values by running an ipconfig /all from cmd

Once this is done, if you try to ping an internal ip address you should be able to reach it, but if you try to ping an external address the request will fail stating that there is no route to host.

We have to add a route to external IPs as follows : sudo ip route add default via
for me my router ip was <IP_ADDRESS>

Finally we have to update our resolver. But WSL2 automatically regenerates /etc/resolv.conf so we have to disable this first. To do so:
vi /etc/wsl.conf  and put the following content in there:

[network]
generateResolvConf = false

After this, you have to restart the linux system : Open a power shell in windows in admin mode and issue:

wsl --shutdown
This will shutdown all the linux instances

now remove resolve.conf and recreate it with the following content:

rm /etc/resolv.conf
recreate it with the following content
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>

Now if u try to ping google.com it should fail (because u have to repeat step 2 , every time u restart ...this is still a WIP for me ;-) , if u know to fix it please share that info) . Once u set the ip and mask properly and ping google.com again. You should get the response.

Thats it! Let me know if it works out for you

The step of:
rm /etc/resolv.conf
recreate it with the following content ...

Could not be done on my windows 10, As soon as "generateResolvConf = false" is set, the resolve file is not accessible. It is actually a link to /run/resolveconf/resolv.conf which cannot be edited even with sudo.
Thus, the simple change to .wslconfig is suggested as the first attempt. (dont forget to wsl --shutdown and strat again after changing the .wslconf)
PS. on windows 11 indider, the .wslconf file is created with the correct swapfile parameter nate at the time of installtion. I guess that on the windows 10, since it was an upgrade from wsl1 to wsl2 that since .wslconf already existed with the old "swap=0" that it was not updated to swapfile.

Don't forget that the issue is 'closed' and fixed

My case is a little bit different. When I'm using desktop VPN (Tunn** Be**), I can't connect to the internet from WSL2 I realize it after turning off the VPN and tried to apt update.

I also lost conection to internet from wsl2 after starting Checkpoint VPN client in Windows. Shutting down the vpn client did not restore internet to wsl2, and neither did net stop LxssManager; net start LxssManager  from Windows side (note: this terminates any open wsl consoles).

I have a similar issue. Strangely it worked when I first convert to WSL2, but no longer works after a reboot.
For me, the windows hosts generates a WSL ethernet card:
    IP: <IP_ADDRESS>
    Mask: <IP_ADDRESS>

For the WSL ubuntu, ifconfig shows this:
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
    inet6 fe80::215:5dff:fe2e:c311  prefixlen 64  scopeid 0x20<link>
    ether 00:15:5d:2e:c3:11  txqueuelen 1000  (Ethernet)
    RX packets 379  bytes 37421 (37.4 KB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 13  bytes 1006 (1.0 KB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

when I try to use ping <IP_ADDRESS>, it comes back with connect: Network is unreachable.
I feel the problem is with the netmask, but not sure how to deal with it given the DHCP.

You are right, looks like this is a dupe of #3438
Try this:
$ sudo ifconfig eth0 netmask <IP_ADDRESS>
$ sudo ip route add default via <IP_ADDRESS>

Where <IP_ADDRESS> and <IP_ADDRESS> are the IP and netmask you got on the WSL interface (run ipconfig on windows and look for the WSL entry).

this fixes the issue for me but i have to do that every time i started wsl VM.
is the real fix coming soon?

you could run a script

Disconnect from VPN, close WSL and reopen it

As @alekzg just disconnect VPN, close WSL and re-open it. I can't believe this hasn't been fixed yet. Anyone want to work on this fix together and get it pushed?

I can't believe windows... This needs to be fixed, wasted my whole morning on this. A simple VPN disconnect and reboot of WSL fixes it. wth going on here.

I don't have any sort of VPN enabled and I'm getting this.

Have you tried turning off Fast Start-Up in the System Settings -> Shut-down Settings?
I've written up the instructions here: https://stephenreescarter.net/wsl2-network-issues-and-win-10-fast-start-up/

For anyone still struggling I have found that allowing incoming traffic on the public profile in the firewall instantly makes DNS resolution work in WSL without having to make any changes to /etc/resolv.conf or having to create /etc/wsl.conf file.
Windows Defender Firewall with Advanced Security -> Windows Defender Firewall Properties -> Public Profile -> Inbound Connections set to Allow.
My company uses Firewall to block certain ports which causes this issue. When I set this to allow all inbound connections DNS resolution inside WSL starts working instantly.

For anyone still struggling I have found that allowing incoming traffic on the public profile in the firewall instantly makes DNS resolution work in WSL without having to make any changes to /etc/resolv.conf or having to create /etc/wsl.conf file.
Windows Defender Firewall with Advanced Security -> Windows Defender Firewall Properties -> Public Profile -> Inbound Connections set to Allow.

My company uses Firewall to block certain ports which causes this issue. When I set this to allow all inbound connections DNS resolution inside WSL starts working instantly.

This works for me. Many thanks!

I should note that for me what worked was uninstalling Check Point Endpoint Security. Even though the program itself wasn't running, uninstalling it fixed this.

The discussions on #4139 ended up fixing this for me.  If your organization uses any of the security baseline policies that ship with Intune, firewall rules are likely the culprit as they implement a deny all incoming rule even for local only interfaces.

You need to make sure that traffic from the network interface in your Linux distro inside WSL2 is routed to the WSL virtual network adapter in your Windows host. If it gets routed anywhere else, you don't get any connectivity to anything outside the Linux vm. VPN connections are notorious for messing that up. I wrote a post about the problem and how you can work around it here: https://janovesk.com/wsl/2022/01/21/wsl2-and-vpn-routing.html

none of this helped but answer on stackoverflow helped
https://stackoverflow.com/a/64057835/1319799
wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns
netsh winsock reset
shutdown /r

Thanks, that worked for me!

In my case, I disabled Hyper-V then it worked finally!

I have questions regarding the potential solution provided.  Basically, I don't know which commands get typed within Windows environment using powershell or cmd versus which get typed within the WSL environment.  Could you clarify please?

ifconfig eth0 netmask <IP_ADDRESS>   <-- type in powershell/cmd or in the WSL ?
ip route add default via      <-- type in powershell/cmd or WSL?

I ask because the ip route command was not recognized by powershell or cmd, and when typed into the WSL (I had to use sudo, so that's also worth mentioning above for us newbies), I get "RTNETLINK answers: File exists"

check this solution. It worked for me after trying all the above suggestions.
Answer here.

Same issue when trying to access network from WSL2. I've uninstalled Docker Desktop on Windows end, rebooted, and it´s working again.

Step1:
run this command on powershell windows
Get-DnsClientServerAddress -AddressFamily IPv4 | Select-Object -ExpandProperty ServerAddresses | Foreach-Object { "nameserver $_" }
Step 2: copy the output of this command
Step 3: go to wsl and type
sudo vi /etc/resolv.conf
Step 4: comment the existing name server and paste the copied lines from step 2
Step 5: save and exit the file.
Step 6: ping the desired domain name and verify the connection.

I can ping but neither can download nor upload

Hi! I've been dealing with this problem for a while, I've tried every solution possible with no results.
The only solution that finally fixed it was completely uninstalling Checkpoint VPN, I even tried to stop every service related to Checkpoint but what solved it at the end was uninstalling it. I even had a ping running in the background and as soon as I uninstalled Checkpoint the ping started to respond.

After factory resetting my TP-Link Wireless Router, the problem was solved. Weird!

In case anyone's coming here from a google search like I did, for me it turns out that a Netgear router was blocking WSL2 internet traffic. Switching to a Google WiFi router solved this issue for me. There's probably some setting in the Netgear router config that controls this but I did not investigate further.

I was getting below error while trying to run wsl --install
A connection with the server could not be established
Error code: Wsl/WININET_E_CANNOT_CONNECT
Solution: I got this error when using Jio mobile hotspot. i changed to airtel hotspot and it works fine. I dont know why it happened, but it works.

Fixed it by using following content in these files.  If files don't exist by default, just create them with given content.
If [/etc/resolv.conf] does not exist, create it
sudo cat /etc/resolv.conf
nameserver <IP_ADDRESS>

if [/etc/wsl.conf] file does not exist, create it
sudo cat /etc/wsl.conf
[network]
generateResolvConf = false

Shutdown WSL and open it again:
wsl --shutdown

I have the similar issue.  Then I found I just configured generateResolvConf to false in /etc/wsl.conf:
# /etc/wsl.conf
[network]
generateResolvConf = false
......

I update the generateResolvConf to true
Shutdown wsl and reopen it again.
It then back to normal.

none of this helped but answer on stackoverflow helped
https://stackoverflow.com/a/64057835/1319799
wsl --shutdown
netsh winsock reset
netsh int ip reset all
netsh winhttp reset proxy
ipconfig /flushdns
netsh winsock reset
shutdown /r

Thanks, that worked for me!

What worked for me was a combination of the above, and in Hyper-V Manager I made sure the switch was set to "Internal Network" (was Private Network). Don't set it to "External Network". I found that creates a bridge and then neither the host nor the guest have internet.

@BilalAhmed-358 Thanks for the explanation. IN CMD, My IPV4 address is "<IP_ADDRESS>", when I run
sudo ip route add default via <IP_ADDRESS>
I got this output "RTNETLINK answers: File exists"
my wsl2 is not connecting to internet.
btw, that command runs fine:
sudo ifconfig eth0 netmask <IP_ADDRESS>

For me, it was Norton's Smart Firewall causing this. I disabled it and problem was solved.

For me is a problem with the router. Resetting works.


Donations Failing

Before you report your issue, please consider perusing the
FAQ and searching the issues
page to see if it has already been reported.
Expected behaviour
Gpay donations go through
Actual behaviour
Donations get 'unspecified error:3'
Steps to reproduce the behaviour
Make a donation, any amount
Please specify the following:

Android version
13
Phone model / brand
Pixel 6
SMS Backup+ version installed
1.6B2
Messaging app
Stock Android Messenger

Jan is no longer working on this project, so he is not taking donations.
I can triage and respond to issues, but I can't push updates to fDroid or PlayStore (See #1059 for details).


Voiceover pagedown

Note to reviews: please ignore the first commit as it is from another branch.
Also note this will not fully fix issue #24330 until the PR #24398 is also merged. It is same to merge this PR and the other in any order.

Changing this to a draft, as I need to fix many tests. Adding the 20ms timeout means many tests need to be updated to have a tick(20). I'll change it to a real PR this this is ready.

@jelbourn and @crisbeto , I address the comments and cleaned up this PR. It's ready for your eyes again 👀 .
After further testing, I determined 0ms would be best for the timeout duration since longer could interfere with repeated keys and cause the entire page to scrolling while pressing and holding pagedown.
I added a code comment with more details on my testing methodology and how I determined 0ms would be best. The code comment is there so we can consider why it was set to 0ms if we ever want to change the timeout value later.


File Explorer support for .stl / .gcode file format.

Description of the new feature / enhancement
So File Explorer support for .stl / .gcode file format.  This would show a iconized version of the file as an image preview.
Scenario when this would be used?
Anyone who is into 3d printing, CAD design. Right now this is only possible with 3rd party add-on.

Supporting information
No response

For stl thumbs, its duplicate of #9695

Omg sorry ☹
Thanks for the heads up.
Stay healthy.
-sean
From: Franky Chen @.>
Sent: October 30, 2021 8:10 PM
To: microsoft/PowerToys @.>
Cc: pbbft @.>; Author @.>
Subject: Re: [microsoft/PowerToys] File Explorer support for .stl / .gcode file format. (Issue #14152)
For stl thumbs, its duplicate of #9695https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FPowerToys%2Fissues%2F9695&data=04|01||9ee15dd8789c437a453f08d99c1bf078|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637712466074420157|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=OB0hdGKtEXjdAbBDBoR9hptX6AT9HGsJw5lFPvF1ZII%3D&reserved=0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FPowerToys%2Fissues%2F14152%23issuecomment-955628855&data=04|01||9ee15dd8789c437a453f08d99c1bf078|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637712466074430110|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Krzd%2FNIevqLqYZbvjt4Kjhp8Mioz54eEln%2Fqb5cXqLk%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAWI7X3RHYG62ZALRM72OSXLUJSXQ3ANCNFSM5HBQTELQ&data=04|01||9ee15dd8789c437a453f08d99c1bf078|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637712466074440071|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=scc9zw27QRX18KXlagVjVy4sJraarjowuK%2BgH6jDwbk%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01||9ee15dd8789c437a453f08d99c1bf078|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637712466074440071|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=QmWHhG7LSP7pEL9PX0WoZ%2Bd7BB%2FZleUKdgR31h3jgVo%3D&reserved=0 or Androidhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01||9ee15dd8789c437a453f08d99c1bf078|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637712466074440071|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=lfgarDa6NXzanKJy292Ub%2FrZFxXpbXj7eXNHS8NhFXo%3D&reserved=0.

Some slicers can add thumbnails directly to the gcode (PrusaSlicer, SuperSlicer, Cura, ...) so we can just read from there the thumbnails!
I've just started coding a thumbnail provider for this, code works fine but it still needs work on the install/register part.

Some slicers can add thumbnails directly to the gcode (PrusaSlicer, SuperSlicer, Cura, ...) so we can just read from there the thumbnails!
I've just started coding a thumbnail provider for this, code works fine but it still needs work on the install/register part.

Hi,
This is 100% true but it doesn't consider .stl files which are the non-sliced 3d files. The screenshot I included are .stl files but it's using a 3rd party thumbnail program in order to generate in File Explorer.
Here is a link to that free add-on: https://github.com/unlimitedbacon/stl-thumb for reference.
This is all a it would be nice thing though vs. really necessary however with 3d printing becoming more mainstream it would be nice for File Explorer to adapt to new file extension types.
if I can assist in any way please let me know.
.pb

For STL, please follow up on #9695

This is added in 0.53, get it at https://aka.ms/installPowerToys

This feature isn't working for me on Windows 11 22H2 with PowerToys v0.71.0
I've tried toggling the switches all off for File Explorer Add-ons, reboot, toggle back on, and reboot.
No changes.
I resorted to using https://github.com/cabbagecreek/Marlin3DprinterTool/ to get the STL to work but this requires having to re-apply the DLL registration.  It doesn't work for .GCode or .3MF (a filetype I wish would work).

While thumbnails from STL are generated from the model item self, Gcode files needs to have embedded thumbnail for this to work.
3MF should generate thumbnails in Windows automatically, but you might need to install 3D Viewer from the Store.


add new line after expanding directive if needed

If the next token after directive expansion is at the same line add new line character to prevent source code to be hidden after macro.

Fixes #143


Bugfix: TDbConnection handling

Use typeof(TDbConnection) for Add and Remove generic overloads.
Changes involve: DbHelperMapper, DbSettingMapper, StatementBuilderMapper.
Resolves #756.

Thanks for this PR. :)

Btw, is there a way we can utilize the IsSubClassOf() method or something similar?

Btw, is there a way we can utilize the IsSubClassOf() method or something similar?

@mikependon what do you mean with that?

Ooopss, forget about my comment above. Thanks for this PR mate :)


[Bug] macOS-latest Xamarin builds fail

Starting today, 7-14-2023, our Xamarin iOS builds that are currently building on macOS-latest images have been failing with the following error.
/Library/Frameworks/Mono.framework/Versions/6.12.0/lib/mono/msbuild/Current/bin/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(283,5): error NETSDK1073: The FrameworkReference 'NETStandard.Library' was not recognized.
This started happening today without any really code changes on our end. We even tried to build older releases that are now also failing.
What do we need to do differently to get our pipelines unblocked?

This repository only covers the GitHub Action: Azure/pipelines Other Azure DevOps questions can be raised via a support ticket or through the community hub: https://techcommunity.microsoft.com/t5/azure-devops/bd-p/AzureDevOpsForum


Application Insights logs not visible in Grafana

Application Insights have logs that are visible only through AI -> Analytics. These are not available on the resources level and therefore also not visible through the Azure Monitor plugin.
With some services, all the relevant logs are on this level. Hopefully I have just configured something wrong :)

If you toggle edit mode in the query window, you should be able to use the 3 part naming syntax to scope any Kusto query you like, e.g.

let traces = app('subscription-name/resource-group-name/app-insights-resource-name').traces;
traces
| where $__timeFilter(timestamp)
| where severityLevel == 3
| summarize count()

This has been flexible enough for me to graph any data available in AI.

This doesn't work for me. Which service type are you using?

I am facing same issue.
The Application Insight instance now have it's own Logs, and I want to query it.
So I don't think I should need another Log Analytic Workspace.
Can't query the logs either way


instead of linking to bolls, could we actually download the text

I find that this is actually of very little use since i cannot search for text (e.g. search for the name Joseph or Canaan), and file links do not work for keywords.
I did try downloading the bible text from Bolls and was successful (ESV was 2.4 MB zipped, 10.6 MB as JSON) but it will be quite a chore to format into the chapters in your layout. BTW I really do like your layout as I can create links down to the verse level.
Thank your for your work on this,
Ian Campbell CPA, CMA, CMC
E<EMAIL_ADDRESS>

It's already possible to build your Bible with text instead of with blocks for verses. This would allow you to search your Bible with Obsidian's search features.
However, I don't know if its possible to add search functionality to the dynamic verses.

Disable the Build with dynamic verses setting before you build your Bible and it will be built with the text of your current translation.

This is absolutely fantastic. Thank you so much.
Ian
On 17 Jul 2024, at 17:35, GsLogiMaker wrote:

Disable the Build with dynamic verses setting before you build your
Bible and it will be built with the text of your current translation.
--
Reply to this email directly or view it on GitHub:
https://github.com/GsLogiMaker/my-bible-obsidian-plugin/issues/20#issuecomment-2234361387
You are receiving this because you authored the thread.
Message ID:
@.***>

God bless!


MC in feed only displaying 2 options on graph

It should show 3. I think this was a recent change, but I could be wrong.

Ready for testing on prod

lgtm


Info Line with spaces only 's issus

How are you using the lua-language-server?
NeoVim
Which OS are you using?
Linux
What is the issue affecting?
Diagnostics/Syntax Checking
Expected Behaviour
Line with spaces only should not show in current cursor line
Actual Behaviour

Reproduction steps
open a lua file
into the insert mode
type someting and press  to start a new line with autoindent
then we will see the Line with spaces only
Additional Notes
No response
Log File
No response

Server dose not know where is your cursor.


Best way to pool reqwest::unstable::async::Client?

What is the best way to pool/share a reqwest::unstable::async::Client?
I'm writing a web application with Hyper 0.11 where each request is potentially handled by a separate core (using my own reset-router, but the model is common I think, c.f. shio). I'm using the one-core-per-thread model, where I am storing the core/handle in thread local storage.
Right now I am using the following:
thread_local!(pub static CLIENT: Client = {
    // this provides a reference to the current thread's core's handle
    cores::with_local_handle(|hdl| Client::new(hdl) )
});

to store the client in TLS. This seems to be working fine, but I don't know if there are any issues with this approach. Would it be better to use some modified version of the reqwest::client::Client sync machinery (e.g., ClientHandle et al.)?

I may not have understood the question entirely, but I think you're asking how to make use of reqwest's Client to take advantage of connection pooling? If so, I think what you're doing is fine. It sounds like you have a Client per thread/core, which works well. As long as your aren't throwing away the Client after every request, the connection pool will be kept around for subsequent requests on that same Client.

Okay, thanks for the response—I think you understand and I think that answers my question. I should have clarified that I am using reqwest here within my app to query an Elasticsearch server.


 No videos load.
F1TV works fine on my phone, on the same network.

Nevermind. Found the issue.


paymentSheetFailed - But there's no more information

Platform

[ ] Web
[ ] iOS
[*] Android

Describe the bug
We're getting paymentSheetFailed - But there's no more information as to why that would be.
To Reproduce
Expected behavior
Some information to be able to debug
Screenshots
Additional context
Usage Product
plugin version 5.4.2
Product Name:
Product URL :
Using Function:

[* ] Payment Sheet / Payment Flow
[ ] Apple Pay
[x] Google Pay
[ ] Identity Verification Sheet

Does this plugin work for Stripe connect accounts?

Just spotted what I need in the documents.


[DISCUSS] Hive Sync will lose some partitions in multi writer scenario

Tips before filing an issue
In hive sync, we get new partition events by getting written partitions since lastCommitTimeSynced field and will sync the newest completed instant time to hive after syncing partitions.  But in multi writer scenario, some instant before lastCommitTimeSynced may be completed after lastCommitTimeSynced have been synced to hive, and the written partitions in those instants will never be included in the future sync procedure.
My opinion is that we can only sync partitions before the oldest inflight instant, just like what we do in archive and incremental clean.
Describe the problem you faced
A clear and concise description of the problem.
To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.
Environment Description

Hudi version :

Spark version :

Hive version :

Hadoop version :

Storage (HDFS/S3/GCS..) :

Running on Docker? (yes/no) :

Additional context
Add any other context about the problem here.
Stacktrace
Add the stacktrace of the error.

You are right, that's why recently we are trying to address the issue by introducing the real transition time on the timeline: https://github.com/apache/hudi/pull/7627, by using the transition time instead, the instants can be sorted by completion time.

since we have a tracking ticket, can we go ahead and close the github issue.

since we have a tracking ticket, can we go ahead and close the github issue.

Hi, I don't really understand how can I go ahead with this issue. Do you mean that I should create a relative jira ticket and close this github issue? Or just close this issue?

Recently we plan to introduce completion time on the timeline:  https://github.com/apache/hudi/pull/7627, after that, we can use this completion time to filter the timeline to resolve this issue.

@stream2000 , do you have intreast to fire a PR to fix the hive meta sync sync  issue, the #7627 has been landed.

Sure, you can assign the issue to me发自我的 iPhone在 2023年5月5日，12:06，Danny Chan @.***> 写道：
@stream2000 , do you have intreast to fire a PR to fix the hive meta sync sync  issue, the #7627 has been landed.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


⚠ Mobitopup has degraded performance

In 1e9aee0, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 3487 ms

Resolved: Mobitopup performance has improved in 1a60754.


ERR_PACKAGE_PATH_NOT_EXPORTED in next-intl 12.4.0

Description
Hello :) The following error occurs when adding
const withNextIntl = require('next-intl/plugin')(
  // This is the default (also the `src` folder is supported out of the box)
  './i18n.ts'
);

to next.config.js.
Failed to load next.config.js, see more info here https://nextjs.org/docs/messages/next-config-error
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './plugin' is not defined by "exports" in /Users/......./node_modules/next-intl/package.json
    at new NodeError (node:internal/errors:387:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:464:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:748:3)
    at resolveExports (node:internal/modules/cjs/loader:493:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:533:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:942:27)
    at /Users/......./node_modules/next/dist/server/require-hook.js:180:36
    at Function.Module._load (node:internal/modules/cjs/loader:804:27)
    at Module.require (node:internal/modules/cjs/loader:1028:19)
    at require (node:internal/modules/cjs/helpers:102:18) {
  type: 'Error',
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

The error didn't occur in version 2.14.0-beta.4 and also not in 2.15.0-beta.1
Mandatory reproduction URL (CodeSandbox or GitHub repository)
https://codesandbox.io/p/sandbox/next-intl-bug-template-app-forked-rsq7su?file=%2Flocales%2Fde.json%3A1%2C1
Reproduction description
Steps to reproduce:

Open reproduction
See logs

Expected behaviour
Normal startup

Same issue here

Hi @chrislicodes,
right, the RSC features are currently only available in beta versions as mentioned in the docs.
If you switch to<EMAIL_ADDRESS>then your app works.
Was there some confusion in regards to the versioning?
I guess it's a bit confusing that 2.14.0-beta.4 didn't turn into 2.14.0 stable. The reasoning is that there was a minor release on the main branch in between, so the new RSC betas will be released on 2.15.0-beta.x for the time being.

Hi @amannn, oh, then I must have confused it. I somehow assumed that the stable 2.14.0 would include the RSC Beta - I just went with 2.15.0-beta.x and everything works as expected and really well together so far 🔥 Looking forward to the merge into main

Right, sorry for the confusion and thanks for following along! 🙌

Thanks for information @amannn. In my case, I've been tricked since I use Dependabot and it automatically created a PR bumping from 2.14.0-beta.4 to 2.14.2 (stable), while I'm using NextJS 13.4 (RSC)


Columbia County, SC, USA

https://services3.arcgis.com/F5762GA30C3SyZFy/ArcGIS/rest/services/Tax_Parcels_2018/FeatureServer/0

might be able to close this out too? https://github.com/openaddresses/openaddresses/issues/1973

Wrong state 😶


Investigation on larger than expected attrition across opening FTM and dragging first stone to monster

Reference: https://docs.google.com/presentation/d/1i7x_mh0oSN8vM1E5zk2A3wCewIDD33D3aKRL2SkYuJc/edit?usp=sharing
We now have tapped_start and level_selected events. Does it look like people aren't making it past tapped_start and the problem might be that they are having technical difficulties in downloading the app?

Hey @burrage ,
Hope you are doing well ;)
Regarding this task please give guidance from where we can start and investigate into the attrition between opening and dragging!
Best Regards
Amit

Party time! Amit has entered the chat!!!
OK cool this is going to be a really good exercise in getting into BigQuery a little deeper and the type of data we collect to understand how far our players are getting within the app and the parts where there might be some friction that we need to fix! This is also so we have someone else on the team besides myself that would know how to navigate the data like this!
So first thing I wanted to share is that, in parallel to this investigation, Jeff is in the process of creating an internal-only dashboard which will display most of these metrics for us without the need for having to query BigQuery every time! However it's still in the works, we will need to add to it over time, and we are running into some hosting issues at the moment that we need to figure out. Also we will most likely want to continue with these series of BigQuery queries because it helps Jeff QA his dashboard to make sure we're in the same ballpark with the numbers because he's actually doing much more fancy things than straight querying (e.g. storing separate intermediate datasets and JOINing them together!, etc.)
Anyway... Here's what we have so far...
I've created this running list of BigQuery queries to start getting rough numbers of how many unique people are going from action to action that we want them to complete.
These queries help form a "funnel" of actions a user would take sequentially (think of these queries visualized like this dashboard view).

To describe the "funnel" dashboard view and how the queries link:

"Learners Reached" is equivalent to how many unique people open the Curious Reader container app for the first time.
Next we move into how many unique people launch a Feed The Monster app.
Here is where we would need to make a query against task #1000 to show how many people successfully download the Feed The Monster web content to be able to play FTM JS (we'll need to write this query when task #1000 is finished).

This takes care of where we would be looking at the data with the Curious Reader container app...

So we next hop on over to the FTM JS data and look at how many unique people tap to start the game.
How many unique people select a level.
How many unique people drag a stone to the monster (and get a puzzle_completed event).
How many unique people end up finishing a level (either successfully or not successfully)-- it doesn't matter to us!
How many unique people end up finishing a level successfully (this would be a proxy to the concept "Learners Acquired"-- that someone has successfully completed the first level of FTM).

Now with that info dump out of the way you might be asking... So Ben... what in the heck am I  even supposed to DO on this task card and didn't we already find out (from that dashboard screenshot) that there is actually a LARGER issue from the amount of people dragging the stone once to successfully completing a level?!?!
All true!!!
What I would need help with here is:
1.) Getting someone else up to speed on BigQuery querying for these types of events we want to be looking at. So taking a look at these queries in the query list, understanding some of the syntax here as it can be a little crazy, and asking questions.
So let's start there before moving on to the next bit :-)
When looking over the query doc, you can see that in some places I started writing queries that allow us to look at how many unique users there for each language. This way we can potentially find if in the system there are certain languages where the user behavior is

Thanks a lot @burrage ,
For the above information🙌

OK part 2 now that we've got those under the belt...
To compare and contrast to Jeff's fancier dashboard for QA, I was trying to build out a chart based on those queries by language with the new app events (tapped_start and selected_level)-- see "CR w/ new events" second tab in the following Google Sheet:
https://docs.google.com/spreadsheets/d/1Kc9xhG69BxjNklH17Rc9wvLqtUCEfoJlGusafE_06QM/edit?usp=sharing

Next step of what we'd like to do... is to make a copy of and modify some of the queries in the Google Doc with all the queries... and constrain those queries to be from March 5th onward to a set end date and make sure that for at least a few languages in the Google Sheet fill out the values for each event type constrained to the time period.
We'd also want to verify with the queries that the data we're getting back decreases for each event and the numbers never increase going from event to event. e.g. opened FTM -> tapped start -> chose level -> dragged stone-- 1000 -> 985 -> 914 -> 800).


Remove createdBy duplicates

There seem to be duplicates in createdBy from time to time, example: Shadow Goggles (item ID 4373)

This is just an issue with me using the old data set everytime instead of rebuilding completely.


Drop Swift versions earlier than 5.8

This PR removes support for Swift versions earlier than 5.8
Motivation:
Following the changes done in swift-metrics on https://github.com/apple/swift-metrics/pull/141, I believe we should align swift-log with the rest of the ecosystem too and support only the last 3 Swift releases.
Modifications:
This PR removes support for Swift versions earlier than 5.8
Result:
Only the last 3 Swift releases are now supported.

@swift-server-bot test this please

Mind checking the soundness (formatting issue)? The CI jobs for old swift we'll remove.

I think the soudness job just needs to be updated to use a newer docker file

No, there was an actual whitespace formatting issue - just fixed it.
The pipeline for api breakage has to be updated to use a newer docker image though. I've asked @yim-lee to take care of the CI changes.

CI updated. @swift-server-bot test this please.

@swift-server-bot test this please

Well, I don't think that worked :D @ktoso / @yim-lee mind triggering the tests again?

@swift-server-bot test this please

@swift-server-bot add to allowlist

@gjcairo We gotta update the breaking change checker script the same way we did in metrics.

branch protection rules adjusted in github -- can you fix the api checker?


Improve tests for annotators of external softwares

Now unit tests for annotators of external softwares, such as mecab and knp, call commands of those softwares internally to check the outputs. This mechanism should be modified.
For example, the current test assumes the output of some software is fixed for some input, but it may be changed with a software update.
Each test should check only the wrapping mechanism of each annotator and should not depend on the output of an external software.

Finally achieved in 93813d5298b08e967cf39d6165bb75019b08c0a5!
The key was jigg.pipeline.IOCommunicator trait and its subclass of StubExternalCommunicator, which  separate IO module, and achieve dependency injection in each annotator.


chore(deps): update common-dev-assets digest to 6ae8a5a

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
21800ff -> 6ae8a5a

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[13pt Pre Clip all raw DEMs for FIM Files

Figure out appx run time savings and increased storage requirements of having DEM's pre-clipped at the HUC level prior to BED runs.

If approved, make the change.

This was taken care of as part of a bigger PR for clipping vectors. See #988

Oops.. should not have closed. This is not done yet.

Aug 9, 2024:  Long since done.


added extraction of title from schema to show as a comment in info()

Note that due to how the extension manager works, for the test file this required adding an option to info to force reloading of the extension manager so that the test extensions would be seen. There may be a better way to handle this. It should handle attributes that use patternProperty, oneOf, allOf, or anyOf constructs. This addresses issue #1137.

I think the windows failure can be solved by adding !=7.1.2 to this line https://github.com/asdf-format/asdf/blob/20741c8043449a1274848cb6d229cf8f14515798/setup.cfg#L56
This is related to #1122.


Non functioning with Liferay (portlet spec) CMS

Hi Magro,
Hope you're still keeping well. I'm trying to use the session manager with Liferay CMS. I have a few things to try but it's an unusual setup with multiple contexts that are all part of the same app. The context.xml gets loaded for each portlet, however I suspect I want a single session shared between them all so I set a static key prefix.
<Context sessionCookiePath="/" >
  <WatchedResource>WEB-INF/web.xml</WatchedResource>
  <Manager className="de.javakaffee.web.msm.MemcachedBackupSessionManager"
     storageKeyPrefix="static:devperf"
     memcachedNodes="n1:devplay01a:11211,n2:devplay01b:11211"
     memcachedProtocol="binary"
     sticky="false"
     sessionBackupAsync="false"
     sessionBackupTimeout="300"
     requestUriIgnorePattern=".*\.(gif|jpg|jpeg|png|wmv|avi|mpg|mpeg|mp4|htm|html|js|css|mp3|swf|ico|flv)$"
  />
</Context>

The addition of sessionCookiePath="/" has stopped the null pointer exception I was getting but I'm now getting:-
WARNING: Could not deserialize session with id 59379AE1574B6D9C0B35F68C64114E3F-n1 from memcached, session will be purged from storage.
de.javakaffee.web.msm.TranscoderDeserializationException: Caught CNFE decoding data

So this may simply be down to the type of data in the session going by this thread:-
https://groups.google.com/forum/#!topic/memcached-session-manager/OrQh2M8ObR8

I got this working with the above session manager, by only enabling the session store for the root context.