# Unable to access Jaeger UI behind Traefik ingress

**URL:** <https://community.traefik.io/t/unable-to-access-jaeger-ui-behind-traefik-ingress/13628>\
**Category:** Traefik v2\
**Tags:** tracing\
**Created:** [March 1, 2022, 9:57am UTC](https://community.traefik.io/t/unable-to-access-jaeger-ui-behind-traefik-ingress/13628 "2022-03-01T09:57:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![golide](https://avatars.discourse-cdn.com/v4/letter/g/9f8e36/32.png) [@golide](https://community.traefik.io/u/golide)\
**Post date:** [March 1, 2022, 9:57am UTC](https://community.traefik.io/t/unable-to-access-jaeger-ui-behind-traefik-ingress/13628/1 "2022-03-01T09:57:25Z")

</div>

0

I have setup Jaeger as per the instructions from this [post](https://medium.com/imaginelearning/jaeger-tracing-on-kubernetes-with-net-core-8b5feddb6f2f). I am unable to access the Jaeger UI in browser when I go to ( **[http://myhost.com/jaeger](http://myhost.com/jaeger)** ). Instead of opening the dashboard the browser opens another website with domain [myhost.com](http://myhost.com). I am attempting to open the dashboard from my PC on the corporate LAN.

Jaeger components are all setup :

```auto
ks -n monitoring get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
jaeger-agent ClusterIP None <none> 5775/UDP,6831/UDP,6832/UDP,5778/TCP 92m
jaeger-collector ClusterIP 10.110.225.20 <none> 14267/TCP,14268/TCP,9411/TCP 92m
jaeger-query ClusterIP 10.111.184.121 <none> 80/TCP 92m
zipkin ClusterIP None <none> 9411/TCP 92m

 ks -n ingress-nginx get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ingress-nginx-controller LoadBalancer 10.111.102.209 17.168.1.181 80:32137/TCP,443:30505/TCP 4d9h
ingress-nginx-controller-admission ClusterIP 10.111.197.68 <none> 443/TCP 4d9h

```

And the hosts file :  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/containo/original/2X/3/37a2692854d8daf81e5f2d417dcbe735f5738971.png)

Jaeger is setup on a k0s cluster (on a Debian 10 Buster instance).

My undersatnding is that the host/Traefik configuration should make the Jaeger UI accessible outside the cluster.

Ingress config is as follows:

```auto
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: traefik
    nginx.ingress.kubernetes.io/rewrite-target: /
    ingress.kubernetes.io/auth-type: basic
    ingress.kubernetes.io/auth-secret: my-auth-secret
  name: jaegerquery-ingress
  namespace: monitoring
spec:
  rules:
  - host: myhost.com
    http:
      paths:
      - path: /jaeger
        pathType: Prefix
        backend:
          service:
            name: jaeger-query
            port:
              number: 80

```

What am I missing ?

---

<div class="post-metadata">

**Author:** ![bluepuma77](https://avatars.discourse-cdn.com/v4/letter/b/a9adbd/32.png) [@bluepuma77](https://community.traefik.io/u/bluepuma77)\
**Post date:** [November 15, 2023, 6:02pm UTC](https://community.traefik.io/t/unable-to-access-jaeger-ui-behind-traefik-ingress/13628/3 "2023-11-15T18:02:18Z")

</div>

I recommend you add k8s ingress tag.