Failed to create first admin user. Not able to use the product
Describe the bug
Installed infisical in Kubernetes following official docs. Accessing application using custom gateway with SSL certificate. No able to create the user. Tried with port-forward same error. Tried enable github authentication, same erro (it does not authenticate with github, keeps asking to create user)
To Reproduce
Check the video https://1drv.ms/v/s!AoHvV-Rb6N9QiLhTQBip3L5Swsq87w?e=p2jrap
Expected behavior
After a successful installation create the admin user should work
Screenshots
If applicable, add screenshots to help explain your problem.
Platform you are having the issue on:
Kubernetes
Additional context
Add any other context about the problem here.
@akhilmhdh can i take this
@gs-kug kindly check your server log and networking.
The admin user is not getting created because of some infra issues
There is no erros in log However the browser has errors with Security-Policy:
ontent-Security-Policy: The page’s settings blocked the loading of a resource (connect-src) at https://us-c.i.posthog.com/i/v0/e/?compression=gzip-js&ip=1&=1723299010244&ver=1.105.6&retry_count=1 because it violates the following directive: “connect-src 'self' wss://nexus-websocket-a.intercom.io https://api-iam.intercom.io/ https://api.heroku.com/ https://id.heroku.com/oauth/authorize https://id.heroku.com/oauth/token https://checkout.stripe.com/ https://app.posthog.com/ https://api.stripe.com/ https://api.pwnedpasswords.com/ http://127.0.0.1:* https://hcaptcha.com/ https://*.hcaptcha.com” _app-3ab697c139afc494.js:1:620219 Content-Security-Policy: The page’s settings blocked the loading of a resource (connect-src) at https://us-c.i.posthog.com/i/v0/e/?compression=gzip-js&ip=1&=1723299022529&ver=1.105.6 because it violates the following directive: “connect-src 'self' wss://nexus-websocket-a.intercom.io https://api-iam.intercom.io/ https://api.heroku.com/ https://id.heroku.com/oauth/authorize https://id.heroku.com/oauth/token https://checkout.stripe.com/ https://app.posthog.com/ https://api.stripe.com/ https://api.pwnedpasswords.com/ http://127.0.0.1:* https://hcaptcha.com/ https://*.hcaptcha.com”
Is this some kind of captcha that is malfunctioning?
I found the problem:
I change the config from:
nameOverride: "infisical"
fullnameOverride: "infisical"
infisical:
image:
repository: infisical/infisical
tag: "v0.78.1-postgres"
pullPolicy: IfNotPresent
autoDatabaseSchemaMigration: true
name: infisical
fullnameOverride: ""
replicaCount: 3
kubeSecretRef: "infisical-secrets"
resources:
limits:
memory: 210Mi
requests:
cpu: 200m
ingress:
enabled: true
hostName: "infisical.kugelbit.work"
postgresql:
enabled: false
redis:
enabled: false
To:
nameOverride: "infisical"
fullnameOverride: "infisical"
infisical:
image:
repository: infisical/infisical
tag: "v0.78.1-postgres"
pullPolicy: IfNotPresent
autoDatabaseSchemaMigration: true
name: infisical
replicaCount: 2
kubeSecretRef: "infisical-secrets"
resources:
limits:
memory: 600Mi
requests:
cpu: 200m
ingress:
enabled: false
hostName: "infisical.kugelbit.work"
postgresql:
enabled: false
redis:
enabled: false
Diff: memory, replicaCount, fullnameOverride, ingress (I'm using custom ingress)
I'm not sure where is the problem as I change all at once. Maybe the memory but there is no log end container restart
Closing as its resolved