From: Bastiaan Wakkie <bwakkie@gmail.com>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Subject: Re: Opening and saving files (crtl-o) (in 9.6 and 9.8) results in 500
 error/Access denied
Date: Sat, 18 Oct 2025 17:20:59 +0200
References: <b0032df7-8365-4ebc-a0d1-add2890ef52d@gmail.com>
To: "pgadmin-support@lists.postgresql.org"
 <pgadmin-support@lists.postgresql.org>
In-Reply-To: <b0032df7-8365-4ebc-a0d1-add2890ef52d@gmail.com>
Message-Id: <72B3573D-7E61-4D20-AE8B-8EB6DA2672F8@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/72B3573D-7E61-4D20-AE8B-8EB6DA2672F8%40gmail.com>
Precedence: bulk

UPDATE:

After upgrading to 9.9 still the same problem.=20

Im getting...
When saving: ... and [! Request failed with status code 500] error popup =
and  =E2=80=9CAccess denied (=E2=80=A6)=E2=80=9D in the Message pane.=20
When opening an already stored file: ... an  [! Request failed with =
status code 500] error  popup.

If Im logged in as pgadmin on the server (the user running the app) and =
I could create a file in the storage directory. I even tried to make one =
file world readable (chmod 777) but still I am getting the above errors. =
I do see any file created directly in the storage.=20

I also started Firefox 144.0 without extensions to see if this was =
causing the problem. But not as I expected as an 500 error indicates =
something server side. But I am ticking off any possible way to trace =
why this problem is happening.

Still nowhere I am able to detect any indication in the log files.

The only thing that works is creating a new folder via the storage =
manager and rename files =E2=80=A6 weirdly enough.

Could it be that I open the query tool always tool in a new tab? I=E2=80=99=
m have trouble finding the setting to disable this btw to test this =
hypothesis.
I also note that options/storage/last storage is set to None. While the =
last directory changes when I move around.

Ps running pgadmin4 in a venv with python 3.13.7

Thx,
Bastiaan

> On 11 Oct 2025, at 12:10, Bastiaan Wakkie <bwakkie@gmail.com> wrote:
>=20
>=20
>=20
> Hi all,
>=20
>=20
> Opening and saving files (crtl-o) (in 9.6 and 9.8) results in 500 =
error/Access denied
>=20
> The rest of the pgadmin4 application is working like normal..
>=20
> I can run any sql queries without problems, just cannot load or save =
any files!
>=20
>=20
> What did I do/remember:
>=20
> 1) recently updated postgresql to 17.5 on manjaro rolling release.
>=20
> 2) I remember that I went to the root of the storage when it started =
to act weird. Not sure this is connected though
>=20
> 3) When I try opening any file stored in the storage, I'm getting ...=20=

> "Request failed with status code 500"=20
> ... error in the application but I cannot find *anywhere* in the logs =
an indication of what is happening (Also not in my postgresql, =
supervisor, nginx or journalctl logs).
>=20
> 4) I updated pgadmin4 from 9.6 to 9.8 like I always do (pip install -U =
pgadmin4) to see if this would fix it but the problem persists.
>=20
> 5) ...I changed CONSOLE_LOG_LEVEL =3D 10 in the hope to see more but =
alas...=20
>=20
> 6) ...I enabled postgresql log to see something comes up there, but no =
postgresql seems quietly doing it's thing..
>=20
> 7) I checked the ...
> STORAGE_DIR =3D "/data/databases/pgadmin4/storage"
> ... and all is owned by the pgadmin user.
>=20
> 8) Via the command line I can add/delete/remove files/directories in =
the storage folder and I will see them in the storage (manager) but =
still unable to open or save any file.
>=20
> 9) BUT when I create a new sql script and try to save it or "save as" =
I am getting an "Access denied" message :
> "Successfully run. Total query runtime: 311 msec. 14603 rows affected. =
Access denied (/new script.sql)Access denied (/new_file.sql)Access =
denied (/two.new.sql)"
> (The message keeps appending my last attempts, btw)
>=20
>=20
> Did anybody else had this problem before?
>=20
> ... and know how to fix it?=20
>=20
> ... or knows a way to track down the 500 error of the app.
>=20
>=20
> or is this git issue material?
>=20
> Cheers,
>=20
> Bastiaan
>=20
>=20
>=20