Issues with Jaeger-UI under Reverse Proxy

[Anand D]

Hi,

We are trying to run Jaeger UI under Reverse Proxy (apache-httpd) and we run into the same issue mentioned under 

https://github.com/jaegertracing/jaeger-ui/issues/42 even though path mapping is relative ( ./ instead of / ) and query-base param is passed.

i.e; We just get a response with empty body only with

<script type="text/javascript" src="./static/js/main.4f0c2202.js"></script>

Our Query UI config :

        

  command:

            - "/go/bin/query-linux"

            - "--config-file=/conf/query.yaml"

            - "--es.server-urls=http://elasticsearch:9200"

            - "--query.base-path=/jaeger"

Reverse proxy conf:

     ProxyPass /jaeger/ http://jaeger-query:16686/

     ProxyPassReverse /jaeger/ http://jaeger-query:16686/

                      where jaeger-query is the K8 service name

Solutions tried:

 - Tried "--query.static-files=/go/jaeger-ui/" in  UI config

 - tried ProxyPass to absolute http://jaeger-query:16686/jaeger/search

Query UI version: 1.6

Questions: 

1) Is there anything else are we missing in UI Config ?

2) Is --query.base-path=/jaeger paramater's use is to only append /jaeger before /search of UI i.e; (myurl/jaeger/search) ?

3) Does the fix for this RP issue gives a complete fix to the issue - https://github.com/jaegertracing/jaeger-ui/issues/42  ? I could see that the thread saying customised builds might be needed under tiffon's comment:

                       One should be able to use a URL prefix with the Jaeger UI.
                        The steps necessary:
                       Checkout the Jaeger UI repo
                        Modify package.json#homepage value to be whatever your prefix is (I tested with "/xyz")
                       Build the UI
                      yarn && yarn build
                      Configure the query-service to serve the generated statis assets (--query.static-files)

Are these changes still necessary? 

Regards,

Anand D

[Yuri Shkuro]

In 1.6 you cannot pass "/go/bin/query-linux" to the Docker image.

I suggest you first get the UI working with a custom prefix without any reverse proxy. If it by itself, wouldn't it indicate the problem in your proxy setup?

[Anand D]

Hi Yuri,

we are using the latest docker image from DockerHub and Yes , Jaeger UI is working perfectly fine without Reverse Proxy with our custom Prefix . The problem occurs only when its under RP. We could say that our Proxy Config is probably correct as we are getting the meta tags and title "Jaeger UI" as response .

[Joe Farro]

Hi Anand,

>I could see that the thread saying customised builds might be needed under tiffon's comment:

The comment you referenced is out of date. The use of --query.base-path should be sufficient to add a prefix to the path / URLs. Seems like that is working fine when without a RP. 

>i.e; We just get a response with empty body only with

><script type="text/javascript" src="./static/js/main.4f0c2202.js"></script>

The relative asset reference will only work if the `<base>` tag is also set:

<base href="/jaeger/" data-inject-target="BASE_URL">

Can you send a sample of a `curl -v` req/resp?

Thanks,

Joe

On Thu, Jul 12, 2018 at 10:48 AM Anand D <d.sri...@gmail.com> wrote:

Hi Yuri,

we are using the latest docker image from DockerHub and Yes , Jaeger UI is working perfectly fine without Reverse Proxy with our custom Prefix . The problem occurs only when its under RP. We could say that our Proxy Config is probably correct as we are getting the meta tags and title "Jaeger UI" as response .

--
You received this message because you are subscribed to the Google Groups "Jaeger Tracing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jaeger-tracin...@googlegroups.com.
To post to this group, send email to jaeger-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jaeger-tracing/5805d953-1da9-4deb-af45-fa0c4f2f513b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Anand D]

Hi Joe,

We pulled the latest Jaeger Query image from Docker-hub and that fixed our issue. QueryUI is working fine now behind reverse proxy.
So, I guess there is a problem with RP only in certain version of image between v1.3 ( where the issue was originally fixed ) and the latest version . I don't know the exact version we were using earlier as the Query image was re-tagged to map our Internal docker Repo.

Thanks for your quick support and response. Loving Jaeger and its UI.

Regards,

Anand D

--

Regards,
Anand D

[Joe Farro]

Hi Anand,

Great to hear it's working and things are going well so far with the UI!

Thanks for letting us know something is amiss with the path prefix between 1.3 and the latest.

By the way, let us know if we should add another firm to the list of adopters :)

https://github.com/jaegertracing/jaeger/blob/master/ADOPTERS.md

Best,

Joe