Open JedMeister opened 1 year ago
Appears to of been fixed upstream, I've not been able to reproduce this on 18.x-dev
It turns out that this only affects the PostgreSQL appliance itself - the others are fine. After a bit of poking around, it seems clear to me that it's something to do with LigHTTPd (the default webserver in the postgres appliance) causing this - all the other apps use Apache and as @OnGle notes - with the same config - it doesn't occur there.
So the issue is something to do with the lighty server config...
Initially I thought that Adminer was broken on our PostrgreSQL appliance. When I browsed to Adminer on the login page I see this:
Straight away I noticed that the default DB is "MySQL" (should be "PostgreSQL"). I selected PostgreSQL from the dropdown and tried logging but it failed. So I was thinking that it must be completely broken.
However, it appears that whilst our default tweaks aren't being applied, it does still work.
The "trick" to make it work, is to ensure that the "Server" box has localhost in it (Note that whilst it is noted in grey, you actually need to explicitly type it in). I.e. this should work:
We need to look a bit closer at this...
[update] this only affects our PostgreSQL appliance, other's work fine. It seems to be something to do with LigHTTPd config!?