Re: Cannot authenticate: "SCRAM authentication requires libpq 10 or later" - Mailing list pgadmin-support

Hello all,

I installed pgadmin4 using "pip install" on a 64bit Raspbian system.

Everything worked well, except for the error message when trying to authenticate to my Postgres server on the same machine.

Here are the steps I followed:

    sudo pip3 install pgadmin4
    sudo mkdir /var/log/pgadmin4 /var/lib/pgadmin4
    sudo adduser pgadmin --disabled-password
    sudo chown pgadmin:pgadmin /var/log/pgadmin4 /var/lib/pgadmin4
    sudo vim /etc/pgadmin/config_system.py        # set paths accordingly
    sudo su - pgadmin
    pgadmin$ python3 /usr/local/lib/python3.9/dist-packages/pgadmin4/setup.py
    pgadmin$ pgadmin4 &

The app boots up fine, and I can access it using a web browser, and log in fine.

NOTE: Configuring authentication for SERVER mode.
Enter the email address and password to use for the initial pgAdmin user account:
Email address: user@e.mail
Password:
Retype password:
Starting pgAdmin 4. Please navigate to http://0.0.0.0:5050 in your browser.
2022-02-20 23:28:30,069: WARNING        werkzeug:       WebSocket transport not available. Install simple-websocket for improved performance.
 * Serving Flask app 'pgadmin' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
2022-02-20 23:28:30,071: WARNING        werkzeug:        * Running on all addresses.
   WARNING: This is a development server. Do not use it in a production deployment.

Only actually logging into a Postgres server fails.

But I have libpq 14 installed and not libpq 10:

pi@raspberry64 $ dpkg -l|grep libpq
ii  libpq-dev                          14.2-1.pgdg110+1                 arm64        header files for libpq5 (PostgreSQL library)
ii  libpq5:arm64                       14.2-1.pgdg110+1                 arm64        PostgreSQL C client library

What am I missing? And how can I fix this? (Except changing the auth method serverside, which I would like to avoid)