Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

JennySwift's avatar

Can't connect Sequel Pro to Forge

I've connected to Forge so many times from Sequel Pro, and now, out of the blue, it won't connect. But I can connect with the command line.

At first, the error Sequel Pro gave me was something like this. So I ran chmod 600 ~/.ssh/id_rsa and tried connecting again. Sequel Pro asked for my SSH password, and the password I entered didn't work.

So I generated a new SSH key and tried again. Again, the password isn't working, and yet I can still connect from the command line.

Any ideas please? It seems pretty weird since it has worked before.

0 likes
18 replies
ejdelmonico's avatar

Did you use the DB and SSH passwords that Forge sent you in the email?

JennySwift's avatar

Yeah, thanks. I've had the credentials saved as a favorite connection in Sequel Pro for a long time.

ejdelmonico's avatar

Are you connecting through the "SSH" tab? Sorry for the questions but I had similar issues in the past because I forgot to use the SSH tab to connect.

JennySwift's avatar

Yeah I am. No problem, I appreciate you trying to help.

JennySwift's avatar

Thanks, mine looks like that too, except for the SSH key I've got ~/.ssh/id_rsa.pub instead of a password.

JennySwift's avatar

Here's the end of the error details it's giving me:

debug1: read_passphrase: can't open /dev/tty: Device not configured debug1: permanently_drop_suid: 505 debug1: No more authentication methods to try. Permission denied (publickey).

ejdelmonico's avatar

That is strange. I wonder if you have to register that new key with forge in the ssh section? Just grabbing at straws here.

JennySwift's avatar

I think you're right, but I'd already done that in order to SSH into Forge from the command line.

jamesfurey's avatar

Hi @JennySwift. Did you ever solve your issue? I'm experiencing the same problem (can no longer connect to my Forge database via Sequel Pro).

JennySwift's avatar

It's really weird-I tried again just recently and it just worked. I don't know why. It worked just after I ran ssh-add ~/.ssh/id_rsa. Not sure how that would explain it, though.

1 like
jamesfurey's avatar
Level 4

Hi @JennySwift and @ejdelmonico,

I found a resolution to my issue – hopefully it'll help with yours.

From the command line – I was originally in ~/.ssh but I'm not sure it makes a difference – run:

ssh-add -l

If you see the following output…

The agent has no identities.

…run:

ssh-add

You may be prompted to enter your passphrase for your private key…

Enter passphrase for /Users/[username]/.ssh/id_rsa:

…in which case, enter your key passphrase and press enter.

You should see something similar to the following output:

Identity added: /Users/[username]/.ssh/id_rsa (/Users/[username]/.ssh/id_rsa)

You can confirm your identity was added by re-running ssh-add -l, which should return something similar to the following output:

4096 SHA256:1234ABCabcETC /Users/[username]/.ssh/id_rsa (RSA)

At this point, try connecting to your Forge database again through Sequel Pro.

With any luck, you'll reconnect without issue.

Good luck!

6 likes
JennySwift's avatar

Glad it's working for you. :) I'm still not sure why it stopped working in the first place, because I think I'd already done that previously.

1 like

Please or to participate in this conversation.