Databases Postgresql When Using Ssh Tunnel I Receive The Fe_sendauth No Password Supplied Error

Databases Postgresql When Using Ssh Tunnel I Receive The Fe S After making changes to the pg hba.conf or postgresql.conf files, the cluster needs to be reloaded to pick up the changes. from the command line: pg ctl reload. from within a db (as superuser): select pg reload conf(); from pgadmin: right click db name, select "reload configuration". note: the reload is not sufficient for changes like enabling. On win 7, they'll happily use ipv6 (and putty will happily tunnel ipv6), so they probably appear to have the origin address of ::1. to confirm if this is the case, look at the postgresql log file on the server. (personally i find it much less of a pain to just configure ssl on my postgresql servers anyway, mind).

Fe Sendauth No Password Supplied A Comprehensive Guide If the client is configured to use a password and the database server is configured to allow connections without a password, but you are still getting the fe sendauth no password supplied error, try providing the correct password. And here is the relevant section from my database.yml. test: adapter: postgresql database: myapp test pool: 5 timeout: 5000 host: localhost username: username password: in the real database.yml, 'username' is replaced with my actual user name that i am logged in as. since the authentication method is defined as 'peer', no password should be. 2. met this problem recently. if you're using postgresql on local machine, and psql works well without logging needed, try pgadmin3's menu file add server properties tab, fill in name field for this connection, leave host field and password field empty, and click ok. from pgadmin docs. I have even tried to configure the .pgpass file in my home directory but to no avail:. you need to create the .pgpass file in the home directory of the account running the psql command, i.e. the postgres account, not yours!.