New to Wave, help needed

[411A]

Hi, and thank you for this free open-source app!

I recently switched from Termius because they deleted my local data to force me into upgrading for sync functionality. I prefer to have full control over my data, so I decided to try your app.

I'm currently on Windows 11 and need to add some VPS connections. I attempted to configure them using connections.json, but unfortunately, it was unsuccessful. Here's my current connections.json:

{
  "myvps1": {
    "batchMode": true,
    "host": "177.230.199.190",
    "identityFile": "\\wsl.localhost/Ubuntu/home/user/myvps1/.ssh/id_rsa",
    "kbdInteractiveAuthentication": false,
    "name": "myvps1",
    "passwordAuthentication": false,
    "port": 22,
    "pubkeyAuthentication": true,
    "type": "ssh",
    "user": "myusername",
    "ssh:identityfile": "\\wsl.localhost/Ubuntu/home/user/myvps1/.ssh/id_rsa"
  }
}

When I tried adding the host using [email protected], I received the following error:

Disconnected from "[email protected]"
error: Connecting to &remote.SSHOpts{SSHHost:"177.230.199.190", SSHUser:"myusername", SSHPort:0}, Error: ssh: handshake failed: Connecting to &remote.SSHOpts{SSHHost:"

It seems the error message is truncated, making it difficult to debug. Could you please clarify why the full error isn't displayed, and what might be causing this issue? I think it's because of my SSH keys, but how actually I can pass the correct path of my SSH keys (stored in WSL2 directory) and the different path to ~/.ssh/config to Wave?!

Wish there was a connections.json sample in docs with some comments explaining each line.

I’m also having trouble accessing files from my local PC through my laptop, similar to how Termius handles SFTP. Could you please guide me on how to set up and access SFTP using this app? (I can see my remote PC in remote connections but I can't see it in files).

Thank you in advance!

[oneirocosm]

Hello! Thanks for bringing this up. There are a few things going on here, so I'll go over each:

Identity Files
I believe the reason you can't connect to your host is because the provided identity file is linking to a file on the WSL. While we can connect to the WSL, we don't have a simple way of reading the identity files from there, at least not yet. The easiest way around this would be to copy the identity file to ~/.ssh on your windows machine and list the path to that in connections.json. To do that, you need to use the "ssh:identityfile" name you used in the last line rather than the "identityFile" one you used earlier. I would do something like

{
  "[email protected]": {
    "ssh:identityfile": ["<path to identity file on the windows host instead of WSL goes here>"]
  }
}

That should work with the current version and will continue to in the future.

As to being able to access the path to the identity file in the WSL, i would absolutely love to do that but am unsure how to in go. Will definitely be on the lookout for a solution though.

Your SSH Configuration Options
A lot of the options in your config only work with the ~/.ssh/configin the current version of the code. With the next version, we are bringing the configuration options that work with ~/.ssh/config and bringing them to the connections.json file as well. But they will require the ssh: prefix like ssh:identityfile has. I don't believe any of the options you listed would be absolutely required, but if you did want them, you could theoretically do something like

{
  "myvps1": {
    "conn:overrideconfig": true,
    "ssh:batchmode": true,
    "ssh:hostname": "177.230.199.190",
    "ssh:identityfile": ["<path to identity file on the windows host instead of WSL goes here>"],
    "ssh:kbdinteractiveauthentication": false,
    "ssh:passwordauthentication": false,
    "user": "myusername"
  }
}

Again, this won't work until the next version, but I think it should work. I'll need to run some similar tests in the meantime to verify it though.

Comments in Examples
We actually do have plans for this. The reason we don't is that plain json doesn't typically allow comments, but if we add hujson support, we should be able to without issue.

More In-depth Logs
The connection error getting truncated is a frustrating oversight that we need to fix. It is still recorded in the log file, just truncated on the frontend. To find it, use the command wsh wavepath log -o. Then you can use ctrl + f to find the error from the frontend. Unfortunately, this will have some issues if the log file gets too long, but for new a new install, you shouldn't have a problem.

SFTP
While we don't have sftp exactly at this point, we do have a somewhat similar interface. Once you ssh into your local PC (note: you cannot ssh into windows machines at this point), you can use the command wsh view <directory on local pc> to open a new widget showing those files as a directory view. For instance, from the ssh session, run the command wsh view ~.

If you have any other questions, please feel free to let me know. Also, let me know if that first connections.json example works for you.

[411A]

Thank you for your kind response and detailed guide, I placed my SSH files inside the following path:
C:\Users\A411\.ssh\myvps_de\
It contains these files: config, id_rsa, id_rsa.pub.
config:

Host myvps_de
    HostName 177.230.199.190
    User myusername
    IdentityFile C:/Users/A411/.ssh/myvps_de/id_rsa

Changed the Wave configuration like below:
connections.json:

{
  "myvps_de": {
    "conn:overrideconfig": true,
    "ssh:batchmode": true,
    "ssh:hostname": "177.230.199.190",
    "ssh:identityfile": ["C:/Users/A411/.ssh/myvps_de/id_rsa"],
    "ssh:kbdinteractiveauthentication": false,
    "ssh:passwordauthentication": false,
    "user": "myusername"
  }
}

For ssh:identityfile, I also tried the following:

• "ssh:identityfile": "C:/Users/A411/.ssh/myvps_de/id_rsa" (Without [])
• "ssh:identityfile": "C:/Users/A411/.ssh/myvps_de/config" (Without [])

For ssh:hostname, I also tried the following:

• "ssh:hostname": "myvps_de" (The name of Host in the config file).

⁉️ I can't make it work! I get the exact same error as before. Is something wrong with my config file or connections.json?!

Notes:

• Permissions to keys are not too open.
• I can SSH using PowerShell without any problems:
  ssh -i C:/Users/A411/.ssh/myvps_de/id_rsa [email protected]

Thank you in advance for your guidance! 🙏