IO_PathNotFound_Path when opening ssh from Dev Hub Businesss

Hello,

To help us better isolate the cause of this behavior, could you please test opening the same SSH sessions from a Windows machine using the same data source?

This will allow us to determine whether the issue is related to macOS-specific behavior (such as file system or permission handling) or if it is tied directly to the data source itself.

Once we know whether the warning also occurs on Windows, we’ll be able to narrow down the root cause and advise on the appropriate next steps.
Thank you for your cooperation, and please let us know the results of your test.

Best regards,

Hi Carl,
I opened the same SSH client from my old Windows PC using the hub as the source and was able to get right in. no warnings or prompts.

Thanks for looking into this.

Mike

Hello,

Thank you for the follow-up.

This is quite odd, I tested the same scenario on my end, and everything appears to be working as expected.
Could you try creating a new SSH entry on RDM MacOS and let me know if the behavior persists?

I look forward to your reply.

Best regards,

I created a new entry as you suggested, but got the same result. The version I'm on is 2025.3.8.5 .NET 9.0.11. I have 2 other people in my department that use RDM and follow the same procedure to transfer thier DB's and they having the same issue.

Thanks for the suggestion.

Hello,

Thank you for the follow-up.

I believe there may be an issue stemming from the original migration from your SQLite database to Hub Personal. Could you share exactly how you performed the migration? I'd like to try reproducing the steps on my end to see if I can replicate the behavior as well.

I look forward to your reply.

Best regards,

Hello

I don't have a deep understanding of the code here, but I believe I understand the issue.

On macOS (I think) RDM won't check the datasource for known SSH hosts, instead it relies on the (standard) file system entry in ~/.ssh/known_hosts.

RDM will first check for the known host in that file (if it exists). It safely checks if that file exists before trying to open it. When you click "Resume and remember...", it will try to add the host and its thumbprint to that file. Again, it checks if the file exists before trying to update it. If the file does not exist, it will try to create it. That last part is critical: it will try to create the file, but not the intermediate directories; so if the .ssh directory doesn't exist, you get this error.

The resolution should be as simple as creating the .ssh directory in your home folder. You wrote that macOS won't let you do that, what error do you get exactly? If you're using Finder, it will warn you that the dot prefix will create a hidden folder, but that's expected. Otherwise on Terminal.app you could run "mkdir ~/.ssh".

Please let me know if that helps.

I will report the underlying issue to the SSH developer.

Thanks and kind regards,

Sorry for the long delay. It seems the issue was fixed in an update. I did uninstalled the previous app and installed the update and I think that's when the dir was created.
I appreciate the assistence.

Mike

Hello,

Thank you for the follow-up.

I will now mark this topic as resolved. Please feel free to reply to this thread if you would like to reopen it.

Best regards,