Failed to connect to manager

[osauldmy]

Hello and thanks for your work.

Unfortunately I cannot make distant work and don't have ideas anymore what else to try. At first I went through neovim quickstart, encountered "exit 1" messages and thought about making it work with cli.

Any command combination I try results in the same error message. Enabling --log-level debug unfortunately doesn't help, log file has same output as stderr. Literally every try results in following error message:

Failed to connect to manager

Caused by:
    0: Failed to connect to unix socket "/var/folders/mb/hjkqt7cn6918zhrb1b4brb380000gp/T/distant.sock"
    1: Failed to connect to unix socket "/var/folders/mb/hjkqt7cn6918zhrb1b4brb380000gp/T/$(whoami).distant.sock"
    2: No such file or directory (os error 2)

distant is in the PATH of the user on remote.

I tried:

• distant launch ssh://user@ip (ip is not an alias here, just a placeholder)
• running distant server listen --daemon on remote and then distant connect ssh://user@ip
• to change --options="ssh.backend=" value from default
• specified correct path to identity file (differs from default)
• set explicit port on remote and used the same locally to connect

My setup:

distant: 0.20.0
ssh: OpenSSH_9.7p1, LibreSSL 3.3.6
host: macos 14
remote: ubuntu 22.04 with same latest distant version

[chipsenkbeil]

@osauldmy did you start a distant manager on your local machine such as via distant manager listen --daemon?

[osauldmy]

Oh, that's embarrassing. Problem was between keyboard and chair :D

I somehow didn't notice the sentence the manager should be started on local machine, I naturally thought it should be started on remote. Thanks

[github-actions[bot]]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.