I know you fixed it already, but the cause was most likely the release of 
Postgresql 18, on the 25th of september.So if you pulled the images again, your 
postgres image updated from 17 to 18, and major releases are not 1-to-1 
compatible. You need to backup your db with 17 image, stop, start the 18 image, 
and restore the db.
CheersAntoine
    Le samedi 27 septembre 2025 à 12:54:11 UTC+2, Keyzer Suze 
<[email protected]> a écrit :  
 
 HiI'm new to containersI'm running this on proxmox lxc  -> debian -> podman 
I'm using this docker-compose.yml
version: '3.8'

services:
  guacd:
    image: guacamole/guacd:latest
    restart: always
    network_mode: bridge

  postgres:
    image: postgres:latest
    restart: always
    network_mode: bridge
    environment:
      POSTGRES_DB: guacamole_db
      POSTGRES_USER: guacamole_user
      POSTGRES_PASSWORD: X
    volumes:
      - /root/guacamole/pdata:/var/lib/postgresql/data

  guacamole:
    image: guacamole/guacamole:latest
    restart: always
    network_mode: bridge
    ports:
      - "8080:8080" # Or change to a different host port if 8080 is in use
    environment:
      GUACD_HOSTNAME: guacd
      POSTGRESQL_HOSTNAME: postgres
      POSTGRESQL_DATABASE: guacamole_db
      POSTGRESQL_USERNAME: guacamole_user
      POSTGRESQL_PASSWORD: X
      #OPENID_ENABLED: "true"
      OPENID_AUTHORIZATION_ENDPOINT: 'X'
      OPENID_JWKS_ENDPOINT: 'X'
      OPENID_ISSUER: 'X'
      OPENID_CLIENT_ID: 'X'
      OPENID_REDIRECT_URI: 'X'
      #OPENID-CLIENT-SECRET: X
      OPENID_CLIENT_SECRET: X
    depends_on:
      - guacd      - postgres
when i started this about 3 days go it worked
did a pull -d and it was working I could connect . i deleted and recreated a 
few times.
But recently I tried again and its failing . 

23:37:08.696 [http-nio-8080-exec-7] WARN  o.a.g.e.AuthenticationProviderFacade 
- The "postgresql" authentication provider has encountered an internal error 
which will halt the authentication process. If this is unexpected or you are 
the developer of this authentication provider, you may wish to enable 
debug-level logging. If this is expected and you wish to ignore such failures 
in the future, please set "skip-if-unavailable: postgresql" within your 
guacamole.properties.
23:37:08.709 [http-nio-8080-exec-7] INFO  
o.a.g.a.b.s.InMemoryAuthenticationFailureTracker - Authentication has failed 
for address "192.168.10.172" (current total failures: 1/5).
23:37:08.710 [http-nio-8080-exec-7] ERROR o.a.g.rest.RESTExceptionMapper - 
Unexpected internal error: 
### Error querying database.  Cause: org.postgresql.util.PSQLException: The 
connection attempt failed.
### The error may exist in org/apache/guacamole/auth/jdbc/user/UserMapper.xml
### The error may involve 
org.apache.guacamole.auth.jdbc.user.UserMapper.selectOne
### The error occurred while executing a query
### Cause: org.postgresql.util.PSQLException: The connection attempt failed.

I'm thinking it can't connect and this is a podman issue - but I also notice 
there as a new image pushed to docker.io - i did try the previous version same 
issue ... 

This might just be me and not know what to do with podman , but it was 
orignally working ...
thanks


  

Reply via email to