Re: authentication fail

From: Michael Eschweiler <michael(dot)eschweiler(at)web(dot)de>
To: khushboo(dot)vashi(at)enterprisedb(dot)com
Cc: pgadmin-support(at)lists(dot)postgresql(dot)org
Subject: Re: authentication fail
Date: 2021-01-30 08:28:40
Message-ID: 02ad2a84-76a8-255a-f366-aaa7ca72156d@web.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Hi Khushboo,

Am 12.01.21 um 05:26 schrieb Khushboo Vashi:
> Hi,
>
> On Tue, Jan 12, 2021 at 12:39 AM Michael Eschweiler
> <michael(dot)eschweiler(at)web(dot)de <mailto:michael(dot)eschweiler(at)web(dot)de>> wrote:
>
> Hi there,
>
> I am using postgresql 12 on Linux opensuse Leap 15.2.
> In 'former times' with my postgresql-db I used pgadmin3. It was nice and
> tiny, and I was happy.
> Now, with pgadmin4 I am not able to connect to my server. There is no
> problem with pgsql nor with knoda even from another computer but with
> pgadmin4 I always get an authentication error. In pg_hba.conf I changed
> all connections to 'trust' - but no way!
> Is there a verbose-mode for pgadmin4 in order to see what is happening?
>
> It should work with pgAdmin as you have no problem with psql.
> You can enable logging to check the issue, please
> refer https://www.pgadmin.org/faq/#8 <https://www.pgadmin.org/faq/#8> to
> enable it.
> Also, you can provide the screen-shot of the error you are getting, so
> we can help you.
>  
>
> Thanks in advance.
> Best regards,
> Michael
>
> By the way: Is there a way to get rid of this annoying nag screen
> telling me every time I start pgadmin that there is a new version? My
> version came with the distro
>
> You can disable the version check by setting UPGRADE_CHECK_ENABLED
> parameter to False,
> refer https://www.pgadmin.org/docs/pgadmin4/4.29/config_py.html
> <https://www.pgadmin.org/docs/pgadmin4/4.29/config_py.html> for the. same.
>

Thanks for the hints and sorry for the delay. Here is what I did after
having deleted everything related to pgadmin in my user directory:
First I created the file config_local.py following the advice at
https://www.pgadmin.org/faq/#8
Then I started pgAdmin4 on a console. During the start I get this message:
--- snip ---
Invalid MIT-MAGIC-COOKIE-1 keyPython path:
"/usr/lib/python3.6/site-packages:/usr/lib64/python3.6/site-packages"
Python Home: ""
Webapp path: "/usr/lib/python3.6/site-packages/pgadmin4-web/pgAdmin4.py"
NOTE: Configuring authentication for DESKTOP mode.
pgAdmin 4 - Application Initialisation
======================================

* Serving Flask app "pgadmin" (lazy loading)
* Environment: production
WARNING: Do not use the development server in a production environment.
Use a production WSGI server instead.
* Debug mode: off
Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid
MIT-MAGIC-COOKIE-1 key
--- snip ---
(don't know if this is ok...)

The browser window with pgAdmin4 opened. In order to see what happened
please revise the attached pdf. As you will see, my trial ended up with
... nothing.

Looking through the pgAdmin4.startup.log (attached) I didn't find
nothing special - this seems ok but I must confess that don't know how
to interprete the messages in pgadmin4.log (attached) and if there is
any hint in order to see what went wrong.

I would appreciate any help in order to get pgAdmin4 working.

Best regards,
Michael

P.S.: The authentication configuring in pg_hba.conf:

# "local" is for Unix domain socket connections only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 md5
host all username xxx.xxx.xx.0/24 trust

(the last line I introduced so that my normal user can access the
database remotely from different machines in my local network.)

Attachment Content-Type Size
pgadmin_d.pdf application/pdf 908.7 KB
.pgAdmin4.startup.log text/x-log 1.4 KB
pgadmin4.log text/x-log 96.4 KB

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Cadstructure Technology 2021-01-30 09:37:57 Unable to installed postgis extension using stack builder
Previous Message Trung Do 2021-01-29 16:38:09 Better use of screen width for query tabs