{"id":391,"date":"2021-07-23T12:28:59","date_gmt":"2021-07-23T12:28:59","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/how-to-resolve-password-authentication-failed-errors-in-postgresql\/"},"modified":"2021-07-23T12:28:59","modified_gmt":"2021-07-23T12:28:59","slug":"how-to-resolve-password-authentication-failed-errors-in-postgresql","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/how-to-resolve-password-authentication-failed-errors-in-postgresql\/","title":{"rendered":"How to Resolve Password Authentication Failed Errors in PostgreSQL\u00ae"},"content":{"rendered":"<\/p>\n
\n
<\/div>\n
\n

Overview<\/h2>\n

If your server returns a Password authentication failed for user error when you try to access MySQL\u00ae resources, the most likely culprit is an invalid or missing PostgreSQL\u00ae user password.<\/p>\n

Solution<\/h2>\n

Check the \/root\/.pgpass<\/code> password file to confirm that the password exists in ::*:postgres:PASSWORD<\/code> format.<\/p>\n

If the password does not exist, you must edit the \/var\/lib\/pgsql\/data\/pg_hba.conf<\/code> file directly. To do this:<\/p>\n

    \n
  1. \n

    Stop Tailwatch. To do this, run the following commands:\n<\/p>\n

    \n
    \n\n\n
    \n
    1\n<\/span>2\n<\/span><\/code><\/pre>\n<\/td>\n
    		\n
    touch<\/span> \/<\/span>etc<\/span>\/<\/span>tailwatchddisable<\/span>\nkillall<\/span> tailwatchd<\/span><\/code><\/pre>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/div>\n<\/li>\n
  2. \n
    Edit the \/var\/lib\/pgsql\/data\/pg_hba.conf<\/code> file and change the md5<\/code> value to the trust<\/code> value.<\/p>\n<\/li>\n
  3. \n
    Restart PostgreSQL. To do this, run the \/usr\/local\/cpanel\/scripts\/restartsrv_postgresql<\/code> command.<\/p>\n<\/li>\n
  4. \n
    Change the PostgreSQL password. To do this, run the following command, where new_pass<\/code> represents the new password:\n<\/p>\n
    \n
    postgres=<\/span># alter user postgres with encrypted password =new_pass postgres=# q<\/span><\/code><\/pre>\n<\/div>\n<\/li>\n
  5. \n
    Edit the \/var\/lib\/pgsql\/data\/pg_hba.conf<\/code> file and change the trust<\/code> value to the md5<\/code> value.<\/p>\n<\/li>\n
  6. \n
    Remove the Tailwatch touch file and restart the service. To do this, run the following commands:\n<\/p>\n
    \n
    \n\n\n
    \n
    1\n<\/span>2\n<\/span><\/code><\/pre>\n<\/td>\n
    		\n
    rm<\/span> \/<\/span>etc<\/span>\/<\/span>tailwatchddisable<\/span>\n\/<\/span>usr<\/span>\/<\/span>local<\/span>\/<\/span>cpanel<\/span>\/<\/span>scripts<\/span>\/<\/span>restartsrv_tailwatchd<\/span><\/code><\/pre>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/div>\n<\/li>\n<\/ol>\n
    Previously, the system stored passwords in the \/var\/lib\/pgsql\/.pgpass<\/code> file.<\/p>\n
    If the \/root\/.pgpass<\/code> file does not exist, the system copies the .pgpass<\/code> file to the \/root\/.pgpass<\/code> file.<\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"
    Overview If your server returns a Password authentication failed for user error when you try to access MySQL\u00ae resources, the most likely culprit is an invalid or missing PostgreSQL\u00ae user password. Solution Check the \/root\/.pgpass password file to confirm that the password exists in ::*:postgres:PASSWORD format. If the password does not exist, you must edit …<\/p>\n","protected":false},"author":1,"featured_media":392,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/391"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=391"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/391\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/392"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=391"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=391"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=391"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}