Unable to login to webhookie server running on linux cloud and local machine

datastax

@arthur i didn't swithc to arm. I just followed the instructions. And ran docker-compose up

arthur

@datastax could you please share AWS logs so that we can find why keycloak is not up?

arthur

@datastax what size of the EC2 instance are you using to run ? it could be that keycloak needs more memory/cpu to start

datastax

@arthur

How do i get the logs out for webhookie on AWS EC2 Ubuntu 20.04?
I have setup and redeployed webhookie on my Apple M1 Mac. Same result. https://smart-otter-27.loca.lt

Please click on the shared localtunnel link. Does it work correctly?

arthur

@datastax could you join to https://meet.google.com/cub-oyny-gsc ?

datastax

webhookie-keycloack | -b 0.0.0.0
webhookie-keycloack | /opt/jboss/tools/docker-entrypoint.sh: line 165: DB_ADDR: unbound variable
webhookie-keycloack exited with code 1

arthur

@datastax could we try a solution now?

datastax

@arthur yes, i'm available

datastax

The webhookie server did not run well on my non M1 Apple machine. It is running normally on my Windows machine.

arthur

@datastax I think for some reason in your Mac terminal where you run docker compose command there is an env variable named DB_VENDOR set to postgres which causes this issue! since keycloak requires DB_ADDR env var to be set if vendor is postgres

let's unset DB_VENDOR before you run docker compose up command or explicitly set DB_VENDOR to h2 in the docker-compose.yml file in order to force keycloak to use h2

I'm sure the default value is h2 and that's why we don't have that set in the docker-compose.yml file. but let's try setting that to see if this resolves the issue

let me know if you're available for a Google Meet .

Thanks