JS and CSS are not served via Traefik when management.path_prefix is set #10631

thoward27 · 2024-02-27T15:23:52Z

thoward27
Feb 27, 2024

Describe the bug

I have deployed RabbitMQ as a docker container in a nomad cluster. I'm routing to it via Traefik. No matter what I try, even though the environment shows the config is present, the management UI is still just a blank page.

Reproduction steps

Spin up a container with rabbitmq:3-management
Add config management.path_prefix = /amqp/
Start server, get blank page.

Here is the response I get

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="X-UA-Compatible" content="IE=edge" />
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>RabbitMQ Management</title>
    <script src="js/ejs-1.0.min.js" type="text/javascript"></script>
    <script src="js/jquery-3.5.1.min.js"></script>
    <script src="js/jquery.flot-0.8.1.min.js" type="text/javascript"></script>
    <script src="js/jquery.flot-0.8.1.time.min.js" type="text/javascript"></script>
    <script src="js/sammy-0.7.6.min.js" type="text/javascript"></script>
    <script src="js/json2-2016.10.28.js" type="text/javascript"></script>
    <script src="js/base64.js" type="text/javascript"></script>
    <script src="js/global.js" type="text/javascript"></script>
    <script src="js/main.js" type="text/javascript"></script>
    <script src="js/prefs.js" type="text/javascript"></script>
    <script src="js/formatters.js" type="text/javascript"></script>
    <script src="js/charts.js" type="text/javascript"></script>
    <script src="js/oidc-oauth/helper.js"></script>
    <script src="js/oidc-oauth/oidc-client-ts.js" type="text/javascript"></script>
    <script src="js/oidc-oauth/bootstrap.js"></script>

    <link href="css/main.css" rel="stylesheet" type="text/css"/>
    <link href="favicon.ico" rel="shortcut icon" type="image/x-icon"/>

    <script type="application/javascript">
      var oauth = oauth_initialize_if_required();

      if (oauth.enabled) {
        if (!oauth.sp_initiated) {
            oauth.logged_in = has_auth_credentials();
            oauth.access_token = get_auth_credentials(); // DEPRECATED
        } else {
          oauth_is_logged_in().then( status => {
            if (status.loggedIn && !has_auth_credentials()) {
              oauth.logged_in = false;
              oauth_initiateLogout();
            } else {
              if (!status.loggedIn) {
                clear_auth();
              } else {
                oauth.logged_in = true;
                oauth.access_token = status.user.access_token;  // DEPRECATED
                oauth.expiryDate = new Date(status.user.expires_at * 1000);  // it is epoch in seconds
                let current = new Date();
                _management_logger.debug('token expires in ', (oauth.expiryDate-current)/1000,
                  'secs at : ', oauth.expiryDate );
                oauth.user_name = status.user.profile['user_name'];
                if (!oauth.user_name || oauth.user_name == '') {
                  oauth.user_name = status.user.profile['sub'];
                }
                oauth.scopes = status.user.scope;
              }
            }
          });
        }
      }

    </script>

<!--[if lte IE 8]>
    <script src="js/excanvas.min.js" type="text/javascript"></script>
    <link href="css/evil.css" rel="stylesheet" type="text/css"/>
<![endif]-->
  </head>

  <body>
    <div id="outer"></div>
    <div id="debug"></div>
    <div id="scratch"></div>
  </body>
</html>

All of the requests to JS and CSS assets all lack the requested prefix.

My environment seems to be defined correctly:

root@73a076296f98:/# rabbitmqctl environment | grep prefix
                          prefix_format => [time," [",level,"] ",pid," "],
                          prefix_format => [time," [",level,"] ",pid," "],
                          prefix_format => [time," [",level,"] ",pid," "],
                          prefix_format => [],level_format => lc,
      {path_prefix,"/amqp/"},

My config file is

root@73a076296f98:/# cat /etc/rabbitmq/rabbitmq.conf
prometheus.return_per_object_metrics = true
management.path_prefix = /amqp/

I have tried

management.path_prefix = /amqp

Expected behavior

I expect for all of the resources to be requested with the amqp prefix

Additional context

Traefik routing looks like

          "traefik2.enable=true",
          "traefik2.http.routers.[[ $qualified_service_name ]]amqp-external.rule=Host(`[[ .service.tags.host ]].[[ .tld ]]`) && PathPrefix(`/amqp`)",
          "traefik2.http.routers.[[ $qualified_service_name ]]amqp-external.middlewares=[[ $qualified_service_name ]]amqp-external-chain",
          "traefik2.http.middlewares.[[ $qualified_service_name ]]amqp-external-chain.chain.middlewares=[[ $qualified_service_name ]]amqp-external-headers",
          "traefik2.http.middlewares.[[ $qualified_service_name ]]amqp-external-headers.headers.customrequestheaders.X-Forwarded-Proto=https"

Initial output from RabbitMQ

##  ##      RabbitMQ 3.13.0
  ##  ##
  ##########  Copyright (c) 2007-2024 Broadcom Inc and/or its subsidiaries
  ######  ##
  ##########  Licensed under the MPL 2.0. Website: https://rabbitmq.com

  Erlang:      26.2.2 [jit]
  TLS Library: OpenSSL - OpenSSL 3.1.5 30 Jan 2024
  Release series support status: supported

  Doc guides:  https://www.rabbitmq.com/docs/documentation
  Support:     https://www.rabbitmq.com/docs/contact
  Tutorials:   https://www.rabbitmq.com/tutorials
  Monitoring:  https://www.rabbitmq.com/docs/monitoring

  Logs: <stdout>

  Config file(s): /etc/rabbitmq/rabbitmq.conf
                  /etc/rabbitmq/conf.d/10-defaults.conf

Answered by thoward27

Feb 27, 2024

My apologies for the noise, this actually does work, I just neglected this part of the docs

The management UI login page will have the URI host:port/my-prefix/ - note that the trailing slash is required in this case.

Navigating to www.domain.tld/amqp failed, but www.domain.tld/amqp/ succeeds.

Thank you for looking at this!

View full answer

michaelklishin · 2024-02-27T15:43:59Z

michaelklishin
Feb 27, 2024
Maintainer

@thoward27 a large majority of management plugin's integration tests are run with and without the HTTP API path prefix.

In other words, the path prefix feature does work for HTTP API clients.

I'm afraid our team does not have the resources to set up Traefik and everything else for non-paying open source users, so please provide an executable way to prove that the HTTP API path prefix "does not work" in a specific case. A rabbitmq.conf and a Python (or anything else our team can read) would suffice.

1 reply

thoward27 Feb 27, 2024
Author

My rabbitmq.conf files contents are

prometheus.return_per_object_metrics = true
management.path_prefix = /amqp/

I am not sure yet how to properly bundle an example here the team could execute. I was more so hoping that someone here could point me in the right direction for next steps to debug this issue. From what I gather, setting the management.path_prefix should be enough, especially if I can find it in the environment output. I am more than happy to do leg work to solve the problem, I've just no leads to pursue right now.

In the background here, I can try and setup a docker-compose file that repros the problem I am seeing.

michaelklishin · 2024-02-27T16:06:46Z

michaelklishin
Feb 27, 2024
Maintainer

A quick glance at Cowboy 2.11 changes (its maintainer is a member of our team) suggests nothing obviously relevant.

Collecting HTTP API request logs and browser console request recording may help clarify what may be going on.

We don't have enough information right now to suggest more.

0 replies

thoward27 · 2024-02-27T16:28:07Z

thoward27
Feb 27, 2024
Author

My apologies for the noise, this actually does work, I just neglected this part of the docs

The management UI login page will have the URI host:port/my-prefix/ - note that the trailing slash is required in this case.

Navigating to www.domain.tld/amqp failed, but www.domain.tld/amqp/ succeeds.

Thank you for looking at this!

2 replies

thoward27 Feb 27, 2024
Author

I had originally misunderstood those docs to think they meant I needed a trailing slash on the management.path_prefix configuration, which made no difference in the end result of www.domain.tld/amqp still not loading correctly.

lukebakken Feb 27, 2024
Maintainer

Thank you for following-up. I implemented the path_prefix feature almost seven years ago (rabbitmq/rabbitmq-management#495) and forgot about the requirement that HTTP request URLs end in /

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

JS and CSS are not served via Traefik when management.path_prefix is set #10631

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 3 comments 3 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

JS and CSS are not served via Traefik when management.path_prefix is set #10631

Uh oh!

Uh oh!

thoward27 Feb 27, 2024

Describe the bug

Reproduction steps

Expected behavior

Additional context

Replies: 3 comments · 3 replies

Uh oh!

michaelklishin Feb 27, 2024 Maintainer

Uh oh!

thoward27 Feb 27, 2024 Author

Uh oh!

michaelklishin Feb 27, 2024 Maintainer

Uh oh!

thoward27 Feb 27, 2024 Author

Uh oh!

thoward27 Feb 27, 2024 Author

Uh oh!

Uh oh!

lukebakken Feb 27, 2024 Maintainer

thoward27
Feb 27, 2024

Replies: 3 comments 3 replies

michaelklishin
Feb 27, 2024
Maintainer

thoward27 Feb 27, 2024
Author

michaelklishin
Feb 27, 2024
Maintainer

thoward27
Feb 27, 2024
Author

thoward27 Feb 27, 2024
Author

lukebakken Feb 27, 2024
Maintainer