Shardool Comments - Answer Overflow

Shardool

•Created by Shardool on 5/22/2025 in #questions-help-bugs

Actions v2 on v3.1.0 returning [internal] An internal error occurred (QUERY-y2u7vctrha)

I was trying to setup the action but never actually managed to get it to work. I only registered the target -> which was with my local backend at http://localhost:8000. I managed to created a trigger following this https://zitadel.com/docs/guides/integrate/actions/testing-response but never managed to test it because I couldn't see the trigger again. loading the console on the trigger page would just throw the mentioned error [internal] An internal error occurred (QUERY-y2u7vctrha)

5 replies

ZZITADEL

•Created by Shardool on 5/22/2025 in #questions-help-bugs

Actions v2 on v3.1.0 returning [internal] An internal error occurred (QUERY-y2u7vctrha)

@Rajat to add the action? I just added the action using the new UI in the console

5 replies

ZZITADEL

•Created by Shardool on 2/3/2025 in #questions-help-bugs

Service user fetching /oauth/v2/token timing out

running v2.67.2

6 replies

ZZITADEL

•Created by Shardool on 2/3/2025 in #questions-help-bugs

Service user fetching /oauth/v2/token timing out

implemented token caching on service users and issue doesn't happen as much but would be nice to know the root cause

6 replies

ZZITADEL

•Created by Shardool on 2/3/2025 in #questions-help-bugs

Service user fetching /oauth/v2/token timing out

zitadel config:

ingress:
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-prod
    nginx.ingress.kubernetes.io/backend-protocol: GRPC
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
  className: nginx
  enabled: true
  hosts:
  - host: auth.***.***
    paths:
    - path: /
      pathType: Prefix
  tls:
  - hosts:
    - auth.***.***
    secretName: zitadel-tls
zitadel:
  configSecretKey: config.yaml
  configSecretName: <secret>
  configmapConfig:
    Database:
      Postgres:
        Admin:
          ExistingDatabase: ***
          SSL:
            Mode: require
          Username: ***
        Database: zitadel
        MaxConnIdleTime: 5m
        MaxConnLifetime: 30m
        MaxIdleConns: 10
        MaxOpenConns: 20
        Port: 5432
        User:
          SSL:
            Mode: require
          Username: zitadel
    ExternalDomain: auth.***.***
    ExternalPort: 443
    ExternalSecure: true
    TLS:
      Enabled: false
  masterkeySecretName: zitadel-masterkey

ingress:
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-prod
    nginx.ingress.kubernetes.io/backend-protocol: GRPC
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
  className: nginx
  enabled: true
  hosts:
  - host: auth.***.***
    paths:
    - path: /
      pathType: Prefix
  tls:
  - hosts:
    - auth.***.***
    secretName: zitadel-tls
zitadel:
  configSecretKey: config.yaml
  configSecretName: <secret>
  configmapConfig:
    Database:
      Postgres:
        Admin:
          ExistingDatabase: ***
          SSL:
            Mode: require
          Username: ***
        Database: zitadel
        MaxConnIdleTime: 5m
        MaxConnLifetime: 30m
        MaxIdleConns: 10
        MaxOpenConns: 20
        Port: 5432
        User:
          SSL:
            Mode: require
          Username: zitadel
    ExternalDomain: auth.***.***
    ExternalPort: 443
    ExternalSecure: true
    TLS:
      Enabled: false
  masterkeySecretName: zitadel-masterkey

config.yml only has the database configuration

6 replies

ZZITADEL

•Created by Shardool on 12/22/2024 in #questions-help-bugs

Issues with using AWS application load balancer

update - I moved to using nginx, and am no longer blocked on this

2 replies

Gaming

Programming