-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Error - Couldn't detect the home directory for XXX_XXX_XXX_XXX #331
Comments
This issue would be easier to solve with debug logs, so please follow these steps:
Besides that, what OS and version of OpenSSH (or similar) is your server running? Any special/unusual server-side config? |
I think i might have the same problem. It also tells me "Could not detect home directory".
|
@wouters It seems like your affected server runs SshReverseProxy. A quick glance at their code makes me think they don't support terminal sessions? It seems to only allow |
I'm facing this issue too - FWIW It only happens when trying to connect to Windows servers, Linux works fine. Exact error is also 'Couldn't detect the home directory for ' Is connecting to a Windows server not supported?
|
Hi. Got next excerpt from logs:
After that:
|
This'll be quite tricky. It looks like the OpenSSH server on Windows starts a command prompt instead of a PowerShell as I expected. Not that the latter is great either, but at least it supports some |
For those having this issue when connecting to Windows OpenSSH servers (@stuieordie), this should be fixed in #338. @gamazind Are you sure that |
Hi @SchoofsKelvin |
Based on the output your shell reported, I assume it's a Cisco router? It looks quite similar to #327, which is still an unresolved issue. In your case, it seems like the extension is also wrongly recognizing your terminal type as PowerShell. Looks like a bug in the fallback shell detection when |
Hi. No, looks it is proprietary SSH |
Well, if it's a proprietary shell that doesn't fit any of the other supported shell types, it'll be quite hard to add support for it. You can try this commit's build (it's just on Should that work fine, it might be able to detect your home directory just fine. Otherwise, add the |
No changes. I`ve checked current shell and SHELL_TYPE=bash (and bash with full path) as well. Additional flags that I have: "DEBUG_SSH2", "-CHECK_HOME". Same behaviour |
I'm having the same problem and my system loads powershell by default. Any resolve yet, it won't let me back in. |
Was able to partially resolve my issue. Deleted config file and reconfigured with new user on remote system. I'm able to login without the error. The system seems to be very sensitive about the path to the remote users home directory. Also, the terminal option does not show up in the list of terminals. I have to manually reconnect it every time. |
Sorry- Still not working. Anything on this issue? |
Can you both post debug logs for the latest
The extension isn't great at handling esoteric server setups regarding weird shells, unusual file system mappings, ... and while I can try to add (limited) support for some of those, it's quite tricky. @edb616321 What terminal option are you talking about? |
I am trying to add a workspace folder from SSH Hosted in Windows Server. But I am getting the following error:
Can you please guide me how I can resolve the issue. I am using the extension for the first time.
Regards
Franklin
The text was updated successfully, but these errors were encountered: