No route to host

Hello,

Thank you for reaching out. I'd like to gather some additional information to help troubleshoot this connectivity issue.

Could you please confirm the following details:

1. What type of entry are you using to connect? (SSH, RDP, VNC, or another protocol)
3. Can you confirm the network configuration of the VM - is it on the same subnet as your Mac, or on a different network?
4. Are you able to ping the server's IP address from your Mac's terminal?

These details will help me identify whether this is specific to RDM or a broader network connectivity issue.

Best regards,

Hello,

I'm using an SSH connection, the server is on the same network and the connection works in the terminal.

Hello,

Thank you for the update.

Could you please follow the troubleshooting steps outlined in this documentation to create SSH Shell logs with verbose output?

https://docs.devolutions.net/rdm/kb/how-to-articles/send-ssh-logs-verbose/

At the same time, I will provide you with a secure link in a private message where you can upload the logs. Once we have them, we’ll be able to investigate further and assist you more effectively.

Please let me know once the logs have been uploaded.

Best regards,

Hello

I recommend checking that Remote Desktop Manager has "Local Network" access in system settings > Privacy & Security > Local Network. If it does, try closing RDM, toggling the setting "Off" and then "On" again seeing if it helps

Kind regards,

@Richard Markiewicz Hello, I tried "Privacy & Security," but it's still the same.

LOG
[4/23/2026 2:34:47 PM] Devolutions.ProtocolsSharp: 2026.1.29.1 OS: macOS
[4/23/2026 2:34:47 PM] Terminal font: Menlo [Menlo, fixed=True]

[4/23/2026 2:34:47 PM] Starting SSH, verbose level: 3
[4/23/2026 2:34:47 PM] Setting up connection
[4/23/2026 2:34:47 PM] Connecting to: 192.168.1.10:22 (IPV_ANY)
[4/23/2026 2:34:47 PM] No route to host


Everything is working fine via the local terminal.

Hello

The error message is quite clear - the kernel is simple telling us there isn't a route to that host. But it's not clear why this would happen with RDM but not Terminal.app. If it was purely a routing table issue, then it would occur in both places.

So what's different? We've ruled out the local network access permission, which would cause this. RDM was listed in the Local Network permissions, right?

The most likely thing I can think of is a misbehaving network extension intercepting socket calls. It might selectively affect some processes but not others (especially when we consider that the SSH binary is a system one versus RDM's .NET socket). Do you have or use a VPN on your machine? Maybe something is still routing traffic even with the VPN disconnected?

I hate to suggest it, but have you tried rebooting your system?

Otherwise, what's the result of `route get 192.168.1.10` in Terminal? Does it show an unexpected interface or gateway?

Thanks and kind regards,