-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot access login screen #1089
Comments
Hi Thanks for the response TypeError: Cannot read properties of null (reading 'credentials') the console image in the docker-compose is console: |
Hi |
We didn't manage to reporoduce it, but we added a few extra measures and debug logging. Would you mind trying |
Closing, since the issue is most likely fixed in |
Hi community
i"m trying to start jitsu on ubuntu 20 (aws EC2 t3.large)
i followed the getting started guideline step to step.
using the docker-compose
i have modified the .env file and run docker-compose up
all is running
when trying to access the ip:3000 the docker console return the followng error:
https://next-auth.js.org/errors#client_fetch_error fetch failed {
docker-console-1 |
docker-console-1 | error: {
docker-console-1 | message: 'fetch failed',
docker-console-1 | stack: 'TypeError: fetch failed\n' +
docker-console-1 | ' at Object.fetch (node:internal/deps/undici/undici:11730:11)\n' +
docker-console-1 | ' at process.processTicksAndRejections (node:internal/process/task_queues:95:5)',
docker-console-1 | name: 'TypeError'
docker-console-1 | },
docker-console-1 | url: 'http://XXX.XXX.XXX.XXX:3000/api/auth/providers',
docker-console-1 | message: 'fetch failed'
docker-console-1 | }
the .env file is (IP masked)
#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
REQUIRED PARAMETERS, PLEASE READ INSTRUCTIONS THOROUGHLY
See https://docs.jitsu.com/self-hosting/quick-start/ for more details
#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Password and login of an initial admin user of Jitsu UI. After initial login, you must change your password!
You can keep those variable empty if you are configuring Jitsu UI via Github auth (see below). In this case first
authorized user will be granted a full access to Jitsu UI.
SEED_USER_EMAIL=admin@myadmin.com
SEED_USER_PASSWORD=1q2w3e4r!
Domain name of your Jitsu server where events will be sent. E.g. https://jitsu.mycompany.com or http://localhost:8080
JITSU_INGEST_PUBLIC_URL=http://XXX.XXX.XXX.XXX:8080
Public URL of your Jitsu UI. E.g. https://jitsu.mycompany.com or http://localhost:3000
JITSU_PUBLIC_URL=http://XXX.XXX.XXX.XXX:3000/
Secrets
It is highly recommended to generate random values for those variables.
You can use
openssl rand -hex 32
to generate random values.CONSOLE_TOKEN=5bf6e8e563327221999c2ffa22641fffbc17238f256837b2e71db6488693f653
BULKER_TOKEN=3a16cc23357c4e339063016c3fef485050f7dfa533f7a35d8cdca412dc45e378
SYNCCTL_TOKEN=644f2ecf89e6e4d321e06f56f49f7e53bd421066666ab07c8a3a9295b3770513
POSTGRES_PASSWORD=228ddf14c0bcbb8ebacfccbfd2152a249c96d693509b5feb799ec8e184b5ad80
#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
OPTIONAL PARAMETERS
#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
JITSU_UI_PORT=3000
JITSU_INGEST_PORT=8080
If you want to have more than one user for Jitsu UI, this could be done via delegating auth to github.
You need to create a new Github OAuth app and set those variables accordingly.
#GITHUB_CLIENT_ID=
#GITHUB_CLIENT_SECRET=
#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Connectors specific
#++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SYNCS_ENABLED=false
EXTERNAL_BULKER_HOST=host.minikube.internal
EXTERNAL_BULKER_PORT=3042
sync controller is running using host network to access 'minikube' w/o problems.
EXTERNAL_SYNCS_PORT=3043
#postgres host how it is reachable from k8s cluster
EXTERNAL_POSTGRES_HOST=host.minikube.internal
EXTERNAL_POSTGRES_PORT=5432
SYNCCTL_KUBERNETES_CLIENT_CONFIG=
to use non-default k8s context
SYNCCTL_KUBERNETES_CONTEXT=
For syncs scheduling
google service account key
GOOGLE_SCHEDULER_KEY=
for Google Ads connector
GOOGLE_ADS_DEVELOPER_TOKEN=
here is the screen shot
Can you help explain what can be the problem?
thanks
Hana
The text was updated successfully, but these errors were encountered: