![]() See this answer (Method 1 preferably) for details. You'll need to set the default user for the new instance as well using /etc/wsl.conf. Wsl -import Ubuntu_WSL1 backup.tar -version 1 127.0.0.1 is an address on the local host, you cannot connect to that from a different host, if you are connecting to a remote host you need to use the 192.168.1. To clone your existing WSL2 to WSL1, create a directory where you want it to be installed, and: wsl -export Ubuntu backup.tar Join any server (it won't log you in as that alt though) 5. Click the Use button (The screen will flash) 4. You can always just run the WSL1 instance when you need to work with this scheduling tool, and continue to use WSL2 if you need it for other use-cases. I use Wurst as its a very very good client but that is a bug I've encounted myself and it is annoying. WSL1 operates on the same NIC as Windows, whereas WSL2 is on a vNIC that is NAT'd behind the Windows host. The simplest solution, if it works for you, is to run a WSL1 instance. I seem to recall this is a normal configuration for Anåonnect, and likely some others as well. ![]() It sounds like only internal traffic may be routed over your VPN. Never found the cause but 'solved' it by adding a retry. For most people, all traffic is routed through the VPN, which causes all networking from within WSL2 to break when the VPN is active. I had a similar problem that strangely occurred on some computers: the first try fails and the second try works. I'm suspecting the VPN doesn't extend to WSL2. I'm on Windows 10 (version 1909) and WSL 2 (Ubuntu 20.04.3 LTS/focal). Is there an Ubuntu firewall in WSL that I need to separately deal with, which could be allowing traffic to some sites and not to others? Other similar issues seem like when they're firewall related, ping doesn't work either and/or they have the same issues on Windows as WSL/Ubuntu. Ping works fine, and I verified port 443 is correct. I've tried the server's IP in case it was DNS-related, as well. ![]() I also figured it could be certificate related, but it doesn't seem like I get to the certificate part of the connection (and again, works fine from Windows, and I didn't do anything special there). I can run the same curl command from WSL to any common secure website (say, ) and it connects.I can run the exact same curl command from CMD in windows (on the same machine) and connect.I would assume something is up with either the server's firewall or my Windows firewall. *connect to port 443 failed: Connection timed out ![]() However, I can't seem to connect to the server. I'm trying to use a command line tool for a scheduler we have installed at my company, and decided to install it in my WSL ubuntu installation. ![]()
0 Comments
Leave a Reply. |