Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
SSH Private Key Problem: "The file couldn't be opened" #633
I've never had any issues connecting to DBs until today, and I can't really figure it out.
What I have
I have a DB deployed in an AWS EC2 instance. I connect to the DB from Postico 1.4.2 on a Mac running High Sierra via SSH, pointing out the private key from the Postico settings, like ~/xx.pem.
xx.pem only contains:
This works just fine!
I now have a new Mac, with Mojave, and Postico 1.5.4. I have the same xx.pem key but when I try to select it in Postico I get a The file couldn't be opened prompt.
Maybe this is some change in Postico 1.5 vs 1.4 but since I can't find 1.4 as a legacy version I haven't been able to downgrade and verify (and I don't dare upgrading on my old machine which still works). Or maybe this has to do with some change in OS X between High Sierra and Mojave.
Unfortunately my knowledge of SSH certificates and keys are too limited to further understand what could be wrong. I have used Postico on other machines too without issue so maybe this points to some change between versions 1.4 and 1.5?
Hope for some help.
Thanks for the quick reply! Embarrassingly enough, your advice #1 did the trick... To compensate for the inconvenience, I just ordered a license :-)…
On Mon, Feb 4, 2019 at 9:45 AM Jakob Egger ***@***.***> wrote: This is most likely an issue with the keychain. Things that may fix the issue: 1. Restart your Mac 2. Create a new user account 3. Redownload Postico See this thread for more info: https://forums.developer.apple.com/thread/46583 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#633 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AtH6TRp0vxwZZXdp7ulIyM_x8XaIZUywks5vJ_MqgaJpZM4agwPQ> .
-- Ola Andersson Norregöksvägen 20 163 54 SPÅNGA Sweden +46725838176