cannot access login screen about jitsu HOT 5 CLOSED

Would you mind sharing stacktrace?

Also, which version of jitsucom/console image you're using

from jitsu.

Hi

Thanks for the response
here is the stack trace

TypeError: Cannot read properties of null (reading 'credentials')
at s.default (http://3.XXX.XXX.16:3000/_next/static/chunks/pages/signin-ecf6422c9bf4d8d7.js:1:2894)
at Xh (http://3.XXX.XXX.16:3000/_next/static/chunks/framework-f3379ba7fbed21eb.js:9:60992)
at x (http://3.XXX.XXX.16:3000/_next/static/chunks/framework-f3379ba7fbed21eb.js:9:119447)
at Vk (http://3.XXX.XXX.16:3000/_next/static/chunks/framework-f3379ba7fbed21eb.js:9:99132)
at http://3.XXX.XXX.16:3000/_next/static/chunks/framework-f3379ba7fbed21eb.js:9:98999
at Jk (http://3.XXX.XXX.16:3000/_next/static/chunks/framework-f3379ba7fbed21eb.js:9:99006)
at Ok (http://3.XXX.XXX.16:3000/_next/static/chunks/framework-f3379ba7fbed21eb.js:9:95762)
at Hk (http://3.XXX.XXX.16:3000/_next/static/chunks/framework-f3379ba7fbed21eb.js:9:94318)
at J (http://3.XXX.XXX.16:3000/_next/static/chunks/framework-f3379ba7fbed21eb.js:33:1364)
at MessagePort.R (http://3.XXX.XXX.16:3000/_next/static/chunks/framework-f3379ba7fbed21eb.js:33:1894)

the console image in the docker-compose is

console:
tty: true
image: jitsucom/console:latest
restart: "unless-stopped"
platform: linux/amd64
environment:
ROTOR_URL: "http://rotor:3401"
BULKER_URL: "http://bulker:3042"
CONSOLE_RAW_AUTH_TOKENS: ${CONSOLE_TOKEN:-default}
BULKER_AUTH_KEY: ${BULKER_TOKEN:-default}
MIT_COMPLIANT: ${MIT_COMPLIANT:-false}
DATABASE_URL: "postgresql://postgres:${POSTGRES_PASSWORD:-default}@postgres:5432/postgres?schema=newjitsu"
REDIS_URL: "redis://default:${REDIS_PASSWORD:-default}@redis:6379"
SEED_USER_EMAIL: ${SEED_USER_EMAIL:-}
SEED_USER_PASSWORD: ${SEED_USER_PASSWORD:-}
GITHUB_CLIENT_ID: ${GITHUB_CLIENT_ID}
GITHUB_CLIENT_SECRET: ${GITHUB_CLIENT_SECRET}
SYNCS_ENABLED: ${SYNCS_ENABLED:-false}
SYNCCTL_URL: "http://syncctl:${EXTERNAL_SYNCS_PORT:-3043}"
SYNCCTL_AUTH_KEY: ${SYNCCTL_TOKEN:-default}
GOOGLE_SCHEDULER_KEY: ${GOOGLE_SCHEDULER_KEY}
JITSU_INGEST_PUBLIC_URL: "${JITSU_INGEST_PUBLIC_URL:-http://localhost:${JITSU_INGEST_PORT:-8080}/}"
JITSU_PUBLIC_URL: "${JITSU_PUBLIC_URL:-${NEXTAUTH_URL:-http://localhost:${JITSU_UI_PORT:-3000}/}}"
NEXTAUTH_URL: "${JITSU_PUBLIC_URL:-${NEXTAUTH_URL:-http://localhost:${JITSU_UI_PORT:-3000}/}}"
UPDATE_DB: "true"
healthcheck:
test: ["CMD", "curl", "-f", "http://console:3000/api/healthcheck"]
interval: 2s
timeout: 10s
retries: 30
extra_hosts:
- "syncctl:host-gateway"
depends_on:
redis:
condition: service_started
postgres:
condition: service_healthy
ports:
- "${JITSU_UI_PORT:-3000}:3000"

from jitsu.

Hi
Any updates on this issue ?

from jitsu.

We didn't manage to reporoduce it, but we added a few extra measures and debug logging. Would you mind trying beta images? Just update to a latest docker-compose from github and set DOCKER_TAG=beta

from jitsu.

Closing, since the issue is most likely fixed in 2.4

from jitsu.