Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ssh tunnel with identity file doesn't work on arm #8135

Closed
Beth1708 opened this issue Nov 15, 2024 · 3 comments
Closed

ssh tunnel with identity file doesn't work on arm #8135

Beth1708 opened this issue Nov 15, 2024 · 3 comments
Assignees
Labels

Comments

@Beth1708
Copy link

I'm trying to set up pgAdmin to connect to a remote server with an identity file on a M1 Max macbook pro

I have the connection working on an intel mac. I replicated the setup to the M1 mac, but when I hit save, I get an error message that says:
Unable to connect to server: connection failed: connection to server at "127.0.0.1", port 61435 failed: fe_sendauth: no password supplied.

On the intel mac, pgAdmin prompts me for the password, but it doesn't on the M1 mac.

I tried it with a key pair that doesn't have a password & it still doesn't work.

The expected behavior is that it will set up the remote server in the server group & I'll be able to see & work with the databases in the remote server (as I can on the intel macbood).

Here's a pic of the error message:
Screenshot 2024-11-15 at 8 47 23 AM

System:
MacBook Pro (2021), Apple M1 Max chip, Sequoia 15.1

@Beth1708 Beth1708 added the Bug label Nov 15, 2024
@Beth1708
Copy link
Author

I tried it with the latest pgAdmin (v 8.13) & one version back (v 8.12) -- neither worked.

@pravesh-sharma
Copy link
Contributor

Hi @Beth1708,

I am not able to reproduce the issue (Attached screenshot of my conf). From the error, it seems you have not passed the PostgreSQL server password. Could you let me know if you are providing the server password while registering it?

image

@yogeshmahajan-1903
Copy link
Contributor

No response from author, hence closing the issue.

@yogeshmahajan-1903 yogeshmahajan-1903 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants