MIME-Version: 1.0
From: Shakir Idrisi <shakir@webuzo.com>
Date: Tue, 10 Jun 2025 12:34:09 +0530
Message-ID: 
 <CAKZfs-q0xwvyL5mQ5-Q5cMSzK0bHa03VjeNRzyCBVze-fa_CeQ@mail.gmail.com>
Subject: Issue with pgAdmin 4 Login Behind NGINX Reverse Proxy at /pgadmin4
 Path
To: support@lists.postgresql.org, pgadmin-support@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000037cf8e0637324e99"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKZfs-q0xwvyL5mQ5-Q5cMSzK0bHa03VjeNRzyCBVze-fa_CeQ%40mail.gmail.com>
Precedence: bulk

--00000000000037cf8e0637324e99
Content-Type: text/plain; charset="UTF-8"

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.

--00000000000037cf8e0637324e99
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><p>Hi,</p>
<p>I&#39;ve installed <strong>pgAdmin 4</strong> on my Linux server and con=
figured it behind <strong>Gunicorn and NGINX</strong>, accessible at:<br>
<code><a href=3D"https://domain.com/pgadmin4/">https://domain.com/pgadmin4/=
</a></code>.</p>
<p>The login page loads correctly. However, after entering valid credential=
s, I&#39;m redirected back to the login page without any error message. Occ=
asionally, I see a <strong>CSRF token</strong> error, which disappears afte=
r a page refresh, but the login still fails.</p>
<p>In the browser console or network tab, I sometimes see <code>401</code> =
errors or issues loading static assets.</p>
<p>Here&#39;s the NGINX configuration I&#39;m currently using to reverse pr=
oxy pgAdmin via a Unix socket:</p>
<pre class=3D"gmail-overflow-visible!"><div class=3D"gmail-contain-inline-s=
ize gmail-rounded-2xl gmail-border-[0.5px] gmail-border-token-border-medium=
 gmail-relative gmail-bg-token-sidebar-surface-primary"><div class=3D"gmail=
-flex gmail-items-center gmail-text-token-text-secondary gmail-px-4 gmail-p=
y-2 gmail-text-xs gmail-font-sans gmail-justify-between gmail-h-9 gmail-bg-=
token-sidebar-surface-primary gmail-dark:bg-token-main-surface-secondary gm=
ail-select-none gmail-rounded-t-2xl"><b>nginx</b></div><div class=3D"gmail-=
overflow-y-auto gmail-p-4" dir=3D"ltr"><code class=3D"gmail-whitespace-pre!=
 gmail-language-nginx"><span class=3D"gmail-hljs-section">location</span> /=
pgadmin4/ {
    <span class=3D"gmail-hljs-attribute">proxy_pass</span> http://unix:/tmp=
/pgadmin4.sock:/;

    <span class=3D"gmail-hljs-comment"># Proxy headers</span>
    <span class=3D"gmail-hljs-attribute">proxy_set_header</span> Host <span=
 class=3D"gmail-hljs-variable">$host</span>;
    <span class=3D"gmail-hljs-attribute">proxy_set_header</span> X-Real-IP =
<span class=3D"gmail-hljs-variable">$remote_addr</span>;
    <span class=3D"gmail-hljs-attribute">proxy_set_header</span> X-Forwarde=
d-For <span class=3D"gmail-hljs-variable">$proxy_add_x_forwarded_for</span>=
;
    <span class=3D"gmail-hljs-attribute">proxy_set_header</span> X-Forwarde=
d-Proto <span class=3D"gmail-hljs-variable">$scheme</span>;

    <span class=3D"gmail-hljs-comment"># Inform pgAdmin it&#39;s served und=
er a subpath</span>
    <span class=3D"gmail-hljs-attribute">proxy_set_header</span> X-Script-N=
ame /pgadmin4;

    <span class=3D"gmail-hljs-comment"># Optional: timeouts and static asse=
t handling</span>
    <span class=3D"gmail-hljs-attribute">proxy_read_timeout</span> <span cl=
ass=3D"gmail-hljs-number">300</span>;
    <span class=3D"gmail-hljs-attribute">proxy_connect_timeout</span> <span=
 class=3D"gmail-hljs-number">60</span>;
}
</code></div></div></pre>
<p>Could you please advise:</p>
<ol>
<li>
<p>Is there something wrong with the proxy setup?</p>
</li>
<li>
<p>Do I need to handle static assets or cookies differently when using a su=
bpath (<code>/pgadmin4</code>)?</p>
</li>
<li>
<p>Are there any additional settings required in the pgAdmin config to work=
 correctly behind a sub-URI with NGINX?</p>
</li>
</ol>
<p>Thanks in advance for your guidance.</p></div></div>

--00000000000037cf8e0637324e99--