Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

Articles in this section

See more

Unable to connect to PostgreSQL database using network connection in Plesk

Avatar
Benjamin Wessel
Updated
Follow
Plesk for Linux kb: technical ABT: Group A

Applicable to:

  • Plesk for Linux

Symptoms

  • Attempts to access PostgreSQL database hosted on the Plesk server using network connection to localhost:5432 fail with the following error:

    psql: FATAL: Ident authentication failed for user "jdoe"

  • Websites using Ruby applications which access PostgreSQL database show the following error:

    500 Internal Server Error
    If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong.

Cause

PostgreSQL is configured to use ident authentication for network connections.

Resolution

  1. Connect to the server via SSH

  2. Change authentication configuration of host type from ident to md5 in pg_hba.conf file. By default it is located for example at the following paths:

    • /var/lib/pgsql/data/pg_hba.conf on RedHat-based systems

    • /var/lib/postgresql/9.1/main/pg_hba.conf on Debian-based systems

    Update the following lines:

    host all all 127.0.0.1/32 ident
    host all all ::1/128 ident
    host all all 203.0.113.2/32 ident

    To the following:

    host all all 127.0.0.1/32 md5
    host all all ::1/128 md5
    host all all 203.0.113.2/32 md5

  3. Restart PostgreSQL service to apply changes:

    # service postgresql restart

Comments

0 comments

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles