GUI loads, but cannot see nodes or VMs (behind nginx reverse proxy)

[dosh]

Hi,

I have an issue where I am unable to expand nodes and VMs in the Proxmox GUI. I can only see the top level datacenter in the left drawer.

The issue is only present when going through the nginx reverse proxy. Going directly to the proxmox server IP, I see VMs just fine.

The issue exists in Chrome, but not in Safari.

As far as I can tell, my nginx conf code is functionally identical to the example given by Proxmox.

Opening the Chrome console, I see a recurring error:
ext-all.js?ver=7.0.0:22 GET https://proxmox.example.domain/api2/json/cluster/resources net::ERR_TOO_MANY_REDIRECTS

My nginx domain.example.conf file looks like this:

server {
    server_name proxmox.example.domain;

    access_log syslog:server=10.24.10.22,tag=nginx main;
    error_log  syslog:server=10.24.10.22,tag=nginx;

    location / {
        proxy_pass https://10.24.10.20:8006;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

        proxy_http_version 1.1;
        proxy_buffering off;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";

        proxy_pass_header Set-Cookie;

        client_max_body_size 0;
        proxy_connect_timeout  3600s;
        proxy_read_timeout  3600s;
        proxy_send_timeout  3600s;
    }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/domain.example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/domain.example.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = proxmox.example.domain) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    server_name proxmox.example.domain;
    listen 80;
    return 404; # managed by Certbot
}

Is this error known? Are there any workarounds?

 

[dosh]

To anybody else that sees this; I was able to solve it. Between testing a million things, I believe it was clearing browser cache that did the trick.

Sometimes the simplest solutions are the best I guess...