SSH connection fails for work hosts resolved through system SSH config

[harshit97]

I'm trying to add a corporate/internal SSH host to Emdash. The same host works from Terminal, but Emdash fails when I enter it manually.

I'm using placeholders here because the real hostname and proxy command are work-internal.

Setup

• macOS
• Emdash 1.1.35
• The host is something like work-host.internal.example
• ssh work-host.internal.example works in Terminal
• ssh -G work-host.internal.example shows that OpenSSH is using a ProxyCommand and agent forwarding
• That config comes from a wildcard Host *.internal.example rule in the system SSH config, not from a concrete host entry in ~/.ssh/config

What happens in Emdash

When I add the host manually and test the connection, Emdash appears to try connecting directly to the hostname. The test fails with:

getaddrinfo ENOTFOUND work-host.internal.example

That looks like Emdash is not using the same resolved SSH config that ssh uses for this host.

What I expected

I expected a way to add this as an SSH-config-backed connection by typing the host/alias and having Emdash resolve it with ssh -G.

This would cover corporate setups where hosts are handled by wildcard rules in /etc/ssh/ssh_config or included system config files, rather than concrete entries in ~/.ssh/config.

[arnestrickmann]

@harshit97, Thanks for the detailed report. We should handle that better. We’ll look into resolving manually entered hostss and update you here shortly!

[thedhruvhegde]

opened a pr for this: #3136