Re: Issue with pgAdmin 4 Login Behind NGINX Reverse Proxy at /pgadmin4 Path

HI,

I have used this command, and I have created a systemd file to start and
stop the service.

*ExecStart=/var/w-data/pgadmin4/pgadmin_venv/bin/gunicorn \*
* --workers 1 \*
* --threads=25 \*
* --bind unix:/tmp/pgadmin4.sock \*
* --chdir
/var/w-data/pgadmin4/pgadmin_venv/lib/python3.11/site-packages/pgadmin4 \*
* --umask 007 \*
* pgAdmin4:app*

Also, when I try multiple times then it will log in and show a blank
dashboard, or sometimes it will show a dashboard but not work properly. In
the console log, I see the following error

[image: image.png]

On Tue, Jun 10, 2025 at 3:26 PM Yogesh Mahajan <
yogesh(dot)mahajan(at)enterprisedb(dot)com> wrote:

> Hi,
>
> Can you please share your guicorn command?
> How many workers are you spawning? It should be 1.
>
> Thanks,
> Yogesh Mahajan
> EnterpriseDB
>
>
> On Tue, Jun 10, 2025 at 12:34 PM Shakir Idrisi <shakir(at)webuzo(dot)com> wrote:
>
>> Hi,
>>
>> I've installed *pgAdmin 4* on my Linux server and configured it behind *Gunicorn
>> and NGINX*, accessible at:
>> https://domain.com/pgadmin4/.
>>
>> The login page loads correctly. However, after entering valid
>> credentials, I'm redirected back to the login page without any error
>> message. Occasionally, I see a *CSRF token* error, which disappears
>> after a page refresh, but the login still fails.
>>
>> In the browser console or network tab, I sometimes see 401 errors or
>> issues loading static assets.
>>
>> Here's the NGINX configuration I'm currently using to reverse proxy
>> pgAdmin via a Unix socket:
>>
>> *nginx*
>> location /pgadmin4/ {
>> proxy_pass http://unix:/tmp/pgadmin4.sock:/;
>>
>> # Proxy headers
>> proxy_set_header Host $host;
>> proxy_set_header X-Real-IP $remote_addr;
>> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
>> proxy_set_header X-Forwarded-Proto $scheme;
>>
>> # Inform pgAdmin it's served under a subpath
>> proxy_set_header X-Script-Name /pgadmin4;
>>
>> # Optional: timeouts and static asset handling
>> proxy_read_timeout 300;
>> proxy_connect_timeout 60;
>> }
>>
>> Could you please advise:
>>
>> 1.
>>
>> Is there something wrong with the proxy setup?
>> 2.
>>
>> Do I need to handle static assets or cookies differently when using a
>> subpath (/pgadmin4)?
>> 3.
>>
>> Are there any additional settings required in the pgAdmin config to
>> work correctly behind a sub-URI with NGINX?
>>
>> Thanks in advance for your guidance.
>>
>