<p>I have installed RabbitMQ to my Kubernetes Cluster via Google Cloud Platform's marketplace.</p>

<p>I can connect to it fine in my other applications hosted in the Kubernetes Cluster, I can create queues and setup consumers from them without any problems too.</p>

<p>I can temporarily port forward port 15672 so that I can access the management user interface from my machine. I can login fine and I get a list of queues and exchanges when visiting their pages. But as soon as I select a queue or an exchange to load that specific item, I get a 404 response and the following message. I get them same when trying to add a new queue.</p>

<pre><code>Not found
The object you clicked on was not found; it may have been deleted on the server.
</code></pre>

<p>They definitely exist, because when I go back to the listing page, they're there. It's really frustrating as it would be nice to test my microservices by simply publishing a message to a queue using RabbitMQ management, but I'm currently blocked from doing so!</p>

<p>Any help would be appreciated, thanks!</p>

<p><strong>Edit</strong><br />
A screenshot provided for clarity (after clicking the queue in the list):
<a href="https://i.stack.imgur.com/nVww2.png" rel="noreferrer"><img src="https://i.stack.imgur.com/nVww2.png" alt="rabbitmq admin"></a></p>

<p>If I try to add a new queue, I don't get that message, instead I get a 405.</p>

Lloyd Powell
<p>I had the same problem as you this morning, and I fix it by using the bellow configuration:</p>

<pre><code>server {
    listen 80;
    server_name rabbitmq.o2c.ovh;
    access_log acces.log;
    error_log error.log;
    location / {
        client_body_buffer_size 128k;
        proxy_send_timeout   90;
        proxy_read_timeout   90;
        proxy_buffer_size    4k;
        proxy_buffers     16 32k;
        proxy_busy_buffers_size 64k;
        proxy_temp_file_write_size 64k;
        proxy_connect_timeout 30s;
        proxy_pass   http://localhost:15672;
        proxy_set_header   Host   $host;
        proxy_set_header   X-Real-IP  $remote_addr;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}
</code></pre>
