Authentik-outpost-tls does not exist - Traefik log error

[morotsgurka]

I'm getting these errors in the traefik logs:

2025-07-08T14:15:08Z ERR Error configuring TLS error="secret networking/authentik-outpost-tls does not exist" ingress=ak-outpost-traefik-proxy namespace=networking providerName=kubernetes

This is the advanced section for the outpost:

log_level: info
docker_labels: null
authentik_host: https://auth.domain.com/
docker_network: null
container_image: null
docker_map_ports: true
refresh_interval: minutes=5
kubernetes_replicas: 1
kubernetes_namespace: networking
authentik_host_browser: ""
object_naming_template: ak-outpost-%(name)s
authentik_host_insecure: false
kubernetes_json_patches: null
kubernetes_service_type: ClusterIP
kubernetes_image_pull_secrets: []
kubernetes_ingress_class_name: null
kubernetes_disabled_components: []
kubernetes_ingress_annotations: {}
kubernetes_ingress_secret_name: authentik-outpost-tls

I'm pretty sure i never added authentik-outpost-tls to the outpost myself? So i assume its the default since its in the documentation also?
Should this secret be created or generated by authentik or cert-manager in some way?

Authentik helm version 2025.6.3

[eazylaykzy]

@morotsgurka were you able to get rid of it?

[morotsgurka]

@eazylaykzy no I didn't, still have the errors. I have a support thread on discord, also with no real solution. Not sure if I just should remove the line from the config or generate the certificate/secret somehow?

[eazylaykzy]

@eazylaykzy no I didn't, still have the errors. I have a support thread on discord, also with no real solution. Not sure if I just should remove the line from the config or generate the certificate/secret somehow?

I removed the line, and replaced with an empty string "", the error persist, I've tried all sort of manipulation.

What worked was adding the cert-manager secret to Authentik namespace with the name authentik-outpost-tls, though creating a certificate within that namespace work too, but looks redundant to me, I don't think that is advisable as we will be creating multiple certificate for a single domain (I use the wildcard certificate, so I don't have to create certificate for every ingress host).

That's the only workaround I could come up with for now.