[Bug]: remote connections not available in dropdown

[ghost]

Current Behavior

Despite the connection manager being populated with ssh-connections when using the GUI to connect to a remote machine, no remote connections are showing up in the dropdown, just the "local" section.

Expected Behavior

Have the dropdown-menu be populated with remote ssh-connections after setting them up the first time and being added to the management file.

Steps To Reproduce

1. Manually connect to a remote machine via SSH via GUI.
2. Have it automatically be added to the management file
3. Dropdown list for remote connections is still empty.

Wave Version

v0.10.4

Platform

Linux

OS Version/Distribution

Ubuntu 24.04

Architecture

x64

Anything else?

Problem is the same, whether using the .deb- oder snap-package.

Questionnaire

• [ ] I'm interested in fixing this myself but don't know where to start
• [ ] I would like to fix and I have a solution
• [ ] I don't have time to fix this right now, but maybe later

[esimkowitz]

Could you send your log file to [email protected]? You can find your logfile location by running wsh wavepath log from within Wave

[heinsenberg82]

I'm having the same issue

[dorel-david]

me too, i have the same issue, using mac M2

[esimkowitz]

Same ask, please send us your logs so we can investigate further

[heinsenberg82]

Same ask, please send us your logs so we can investigate further

sent

[dorel-david]

Same ask, please send us your logs so we can investigate further

sent

[esimkowitz]

Is it always empty or does it populate if you close the connection switcher and reopen it?

[dorel-david]

Is it always empty or does it populate if you close the connection switcher and reopen it?

from my side, it is always only show the local one, even if connected to the remote server, the list still show the local one(even reopen).

[esimkowitz]

What does your ~/.ssh/config look like?

[dorel-david]

What does your ~/.ssh/config look like?

i don't have this file, but i had look in the doc, it should support internal config/connections.json file right?

[esimkowitz]

Does the file exist? Or is it missing completely? I'm trying to correlate if this is a known issue or not.

[dorel-david]

Does the file exist? Or is it missing completely?

it is missing completely, should i create it manually?

[heinsenberg82]

Let me say that just f%4#ng out of nowhere my remote connection is now appearing on the dropdown.... 😅🤷‍♂️

[dorel-david]

me, too, after a create the ~/.ssh/config file, and create a connection to the file, now it show in the dropdown, even the internal connection can show. but when i delete the config file content(file still exist), the dropdown connections disappear again.

[heinsenberg82]

me, too, after a create the ~/.ssh/config file, and create a connection to the file, now it show in the dropdown, even the internal connection can show. but when i delete the config file content(file still exist), the dropdown connections disappear again.

Weird. I already had a ~/.ssh/config file. Nothing changed.

[dorel-david]

me, too, after a create the ~/.ssh/config file, and create a connection to the file, now it show in the dropdown, even the internal connection can show. but when i delete the config file content(file still exist), the dropdown connections disappear again.

Weird. I already had a ~/.ssh/config file. Nothing changed.

you need to fill something in the config file, cannot let it stay empty. then you can show:

[heinsenberg82]

me, too, after a create the ~/.ssh/config file, and create a connection to the file, now it show in the dropdown, even the internal connection can show. but when i delete the config file content(file still exist), the dropdown connections disappear again.

Weird. I already had a ~/.ssh/config file. Nothing changed.

you need to fill something in the config file, cannot let it stay empty. then you can show:

That's my point, my Wave Terminal config file was also already populated. I don't know what have changed in order to the dropdown is properly working now.

[fraymackers]

Same issue for Windows

[esimkowitz]

this should be fixed in the latest beta, can you check if you still have the issue there?

[esimkowitz]

Checking again, is this fixed? Going to close next week if I don't hear back.

[heinsenberg82]

Checking again, is this fixed? Going to close next week if I don't hear back.

The issue keeps occurring. For example, I just opened the program, and when I tried to create a new terminal, it correctly displayed my remote connections. However, when I tried to open a file view, only the local connections were shown.

[esimkowitz]

Are you enabling WSH for your remote connections? Only connections with WSH enabled will show up in the preview widget

[heinsenberg82]

Are you enabling WSH for your remote connections? Only connections with WSH enabled will show up in the preview widget

For reasons I don't know, this was my configuration:

"[email protected]:2222": {
    "conn:wshenabled": false
  },

After I changed conn:wshenabled to true, it seems to have a conflict with ZSH:

And now, when I try to open the files window, the window shows this error:

Error: no route for "conn:[email protected]:2222"

Error: no route for "conn:[email protected]:2222"
    at file:///C:/Users/user/AppData/Local/Programs/waveterm/resources/app.asar/dist/frontend/assets/index-q3GoV2Ly.js:20517:19
    at Generator.next (<anonymous>)
    at resume (file:///C:/Users/user/AppData/Local/Programs/waveterm/resources/app.asar/dist/frontend/assets/index-q3GoV2Ly.js:66:29)
    at file:///C:/Users/user/AppData/Local/Programs/waveterm/resources/app.asar/dist/frontend/assets/index-q3GoV2Ly.js:67:68

[esimkowitz]

Does restarting Wave help?

[heinsenberg82]

Does restarting Wave help?

Nope. Actually, restarting the application now presents this error popup, both in the terminal and file views.

Disconnected from "[email protected]:2222"

unable to use wsh: error opening domain socket listener: unable to request connection domain socket: ssh: [email protected] request denied by peer

[Button: "always disable wsh"]

Btw, there's nothing wrong with my SSH connection, I can connect normally on my server.

[esimkowitz]

Can you share the (sanitized) config for your remote? Also what OS are you running on the remote?

[heinsenberg82]

Can you share the (sanitized) config for your remote?

Do you mean the .waveterm\config\connections.json file?

{
  "[email protected]:2222": {
    "conn:wshenabled": true
  },
  "wsl://Debian": {
    "conn:wshenabled": true
  }
}

Also what OS are you running on the remote?

It's an Openmediavault 7 NAS. Debian GNU/Linux 12 (bookworm) x86_64 OS.

[esimkowitz]

Sorry, I meant your ~/.ssh/config configuration. Obviously leave out anything sensitive, I just want to see what options you're using

[heinsenberg82]

Sorry, I meant your ~/.ssh/config configuration. Obviously leave out anything sensitive, I just want to see what options you're using

No worries. Here it is:

Host 192.168.28.12
  HostName 192.168.28.12
  Port 2222
  User user