-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wthrr with WSL1 Windows 10 #138
Comments
Is it possible to check the network settings for your WSL system? Many hypervisors allow for the detailed configuration of the network settings of their maintained virtual machines. And, as far as I know, WSL is just a virtual machine, as well, with Microsoft Windows as host and hypervisor. If I remember correctly, settings regarding a WSL can be viewed and edited within a PowerShell using the appropriate command line instructions. When you try to ask for your WSL's settings on a PowerShell, which output do you receive? |
Hi |
Hey @dtantono, sorry for the inconvenience. Also about weak support on windows, I left the windows eco system some while ago and rarely come back just for some bug fixes. Though VPN works for me on a linux based system there are definitely potential issues. But since you tried the auto location: the way wthrr currently works, it would try to provide the weather for the ip location of you VPN, which probably wouldn't be what your are looking for anyway? Could you try to specify a city in you call and check if this works for you? Thanks alot @kevinmatthes for helping out! |
Hi |
So coordinates work but |
not just London. but, everywhere with VPN cannot be used with WSL1 on Windows. |
Yes, it was meant to ask if requesting a city (not just london) via coordinates works with a VPN enabled, but requesting it by name does not. This would be something to investigate. |
Hi

I have a question: the wthrr installed properly on Ubuntu & Debian with Windows subsystem for Linux and I got nerd fonts as well. But, when I tried to run it. it throws this error messages (on Powershell it works though): 0: error trying to connect: dns error: failed to lookup address information: Temporary failure in name resolution
1: dns error: failed to lookup address information: Temporary failure in name resolution
2: failed to lookup address information: Temporary failure in name resolution
So, I suppose this wthrr does not work on WSL1. Is that so?
The text was updated successfully, but these errors were encountered: