-
Notifications
You must be signed in to change notification settings - Fork 110
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
[Bug]: error: timeout waiting for connserver to register #987
Comments
@juergenbarth, what kind of authentication does your Synology server use for SSH? |
@esimkowitz : It uses ssh-key. |
Do you have a password or a passphrase on your key? Is it stored in your SSH config or in an SSH Agent? Also do you see anything weird in ~/.waveterm/waveapp.log when you try to connect? |
@esimkowitz There are no passwords on the key and it is stored in SSH config. Here are a few interesting lines from ~/.waveterm/waveapp.log, taken from the latest connect attempt (changed the username 😎): 2024-10-08 18:47:23 [wavesrv] 2024/10/08 18:47:23.899730 SETMETA: block:a4a96f51-280d-4759-bb10-c53f95a17421 | map[connection:[email protected] file:] |
@oneirocosm any ideas? |
@juergenbarth do you know if your NAS allows for mounting domain sockets over SSH? We use this mechanism to establish a connection between our app and your remote server. Also, what OS does Synology use? Is it Linux? |
@esimkowitz All I can tell you is that this used to work with WaveTerm 0.7 and that I can log on this way directly from macOS Terminal via the ssh [email protected] command. The Synology OS is a Linux derivative. |
I wonder if the OS has some safeguard that is preventing us from running our WSH helper binary on the remote. At the moment, all connections established via our connections UI require our WSH helper to be loaded onto the remote before we complete the connection |
Though we had a similar mechanism in the old app so it'd be weird if that were the regression... |
Could it be related to the shell on the Synology? We only have sh not bash or zsh... |
@juergenbarth do you see the wsh binary in ~/.waveterm/bin on your Synology NAS? |
@esimkowitz Yes it's there, the permissions are 777. I can execute it, it brings the usage info. It even gets updated to the latest release |
That's really interesting. What about the |
@oneirocosm /tmp does exist and has permissions drwxrwxrwt. |
I'm still not completely sure why the domain socket isn't connecting, but we found a different bug which may end up resolving this one. I'll keep you posted as we work on the fix. |
I just realized i was ambiguous about something. The /tmp dir that exists with drwxrwxrwt, was that on your host or on the NAS? I meant to have you check on the NAS. Also, if it does exist on the NAS, is it possible for you to create a file there while logged in as the user you are trying to connect to? |
@oneirocosm Yes it is on the NAS:
|
Current Behavior
When trying to connect a tab to a Synology NAS via ssh, I get the following error:
Disconnected from "[email protected]"
error: conncontroller [email protected] start wsh connserver error: timeout waiting for connserver to register
No connection is established.
Expected Behavior
The program should connect to the server without any problems, as it does with my Ubuntu based Linux server.
Steps To Reproduce
Wave Version
Client Version 0.8.8 (202410012200)
OS
macOS 14.7
Architecture
arm64
Anything else?
No response
Questionnaire
The text was updated successfully, but these errors were encountered: