[Query] Unable to connect via OpenSSH

[Vivraan]

No description provided.

[therealkenc]

I cannot connect to the requested remote through Windows LibreSSL but not through the WSL OpenSSL.

Assume you mean can connect with win32 LibreSSL, or the 'but' doesn't make sense in the sentence above.

There is no way to tell what externality changed between "only a few days ago". There is no path to reproduce this. Please collect WSL logs and post the backlink to the feedback item here. Also please identify any third-party networking software that has been installed on Windows. Also your build number, and whether you are running WSL1 or WSL2, per the template that was deleted.

[Vivraan]

Also please identify any third-party networking software that has been installed on Windows.

@therealkenc could you give me examples of such software? Are VPNs such software? I believe I don't have anything like this running at the moment.

[Vivraan]

I cannot connect to the requested remote through Windows LibreSSL but not through the WSL OpenSSL.

Assume you mean can connect with win32 LibreSSL, or the 'but' doesn't make sense in the sentence above.

Indeed - I've fixed the grammar!

[Vivraan]

I'll update the WSL Log once I re-enable virtualisation on my machine.

[therealkenc]

Could you give me examples of such software? Are VPNs such software?

Usually VPNs. Anti-virus software. Anything that might cause your setup to not work, but a clean Windows install to be okay.

If you updated windows and there is no route to anywhere (ping 1.1.1.1), there are a few open issues from people experiencing that. If you are only having trouble reaching 192.168.1.49 on your LAN, then I unfortunately have no guesses as to what changed in your environment since a few days ago.

[Vivraan]

ping 1.1.1.1 works from Powershell.

I'll update the WSL Logs, they will be more relevant.

[therealkenc]

ping 1.1.1.1 works from Powershell.

I take that to mean you can't access the network at all from WSL. Cannot access anywhere on the Internet.

What is the output of:

$ ip address
$ ip route

That will at least show the state of your WSL network.

Disabling Windows Firewall is one thing to try. If you've got a Windows backup you can roll back to ("a few days ago") that is an option. Desperate measures....

[Vivraan]

I think I haven't set up backups on this machine. I do remember that when I had tried connecting to the remote using its ethernet address (not the wireless LAN one) it had worked.

[Vivraan]

What is the output of:

$ ip address
$ ip route

That will at least show the state of your WSL network.

[Vivraan]

@therealkenc Strangely, connecting with SSH seems to be working now. Very odd.

Should I send a log regardless?

[therealkenc]

Not if it is working, no. Happy to hear you are live. If it goes down again, you could collect logs in a fail condition. Better would be to try to figure out what is changing. Could be network related. Some software running or not running. There isn't enough to work with here to guess.

[Vivraan]

Should I close the issue or wait for a failure and report back?

[therealkenc]

Close the issue once you are satisfied it is working. When is up to you.