Authentik widget error: TypeError: f.reduce is not a function #4791
DescriptionI have Authentik deployed in a kubernetes cluster, with an ingress configured for the authentik-server service. Homepage is able to see that the service is running from the Ingress annotations, but I get a Here's the full error from homepage homepage versionv0.10.9 (b5f4daa, Jan 6, 2025) Installation methodOther (please describe above) ConfigurationKubernetes annotations:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
cert-manager.io/cluster-issuer: letsencrypt
field.cattle.io/publicEndpoints: >-
[{"addresses":["192.168.2.201"],"port":443,"protocol":"HTTPS","serviceName":"authentik:authentik-server","ingressName":"authentik:authentik-server","hostname":"authentik.redacted.net","path":"/","allNodes":false}]
gethomepage.dev/app: authentik
gethomepage.dev/enabled: 'true'
gethomepage.dev/group: Infrastructure
gethomepage.dev/href: https://authentik.redacted.net
gethomepage.dev/icon: authentik.png
gethomepage.dev/name: Authentik
gethomepage.dev/namespace: authentik
gethomepage.dev/pod-selector: ''
gethomepage.dev/weight: '5'
gethomepage.dev/widget.api: redacted
gethomepage.dev/widget.failedLoginsLast24H: 'true'
gethomepage.dev/widget.loginsLast24H: 'true'
gethomepage.dev/widget.type: authentik
gethomepage.dev/widget.url: https://authentik.redacted.net
gethomepage.dev/widget.users: 'true'
meta.helm.sh/release-name: authentik
meta.helm.sh/release-namespace: authentik
creationTimestamp: '2025-02-14T04:56:44Z'
generation: 2
labels:
app.kubernetes.io/component: server
app.kubernetes.io/instance: authentik
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: authentik
app.kubernetes.io/part-of: authentik
app.kubernetes.io/version: 2024.12.3
helm.sh/chart: authentik-2024.12.3
spec:
ingressClassName: traefik
rules:
- host: authentik.redacted.net
http:
paths:
- backend:
service:
name: authentik-server
port:
number: 80
path: /
pathType: Prefix
tls:
- hosts:
- authentik.redacted.net
secretName: authentik-certContainer LogsNothing relevant to kubernetes, but the log is filled with these, even though I applied the recommended service account settings. Browser LogsNo response TroubleshootingFollowed the troubleshooting guide. Ensured no trailing / in the url. Using |
Answered by
CyberAustin
Feb 18, 2025
Replies: 3 comments 2 replies
|
I also just tested the 3 API endpoints in https://github.com/gethomepage/homepage/blob/dev/src/widgets/authentik/widget.js from inside the homepage container, and they all appear to be working. At least, provided the below is normal for |
0 replies
|
The logs show a 403 error, 403 is auth, presumably because you don’t have a key set |
2 replies
|
It's set. It's in the Ingress annotations |
|
Wait. Okay, I see it. I had it set as |
Answer selected by
CyberAustin
|
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Wait. Okay, I see it. I had it set as
widget.apiand notwidget.key. Working now. Thanks for the hint.