Keycloak-17.0.0 Account Console not loading

I’m trying to evaluate Keycloak-17.0.0

When I access account console with the below URL
https://<domain-name>/realms/<realm-name>/account/ the account console just shows a loader like this.
image

Browser console reports the below error

https://<domain-name>/js/keycloak.js net::ERR_ABORTED 404 (Not Found)
        
Uncaught ReferenceError: Keycloak is not defined at (index):125:28

I’m running Keycloak-17.0.0 on JDK11 (Eclipse Adoptitum Temurin 11.0.14) behind a Nginx proxy.

Below is my keycloak configuration.

# The proxy address forwarding mode if the server is behind a reverse proxy.
proxy=passthrough

# Hostname for the Keycloak server.
hostname=<domain-name>

# Hostname for the Keycloak server admin console.
hostname-admin=<admin-domain-name>

hostname-strict-backchannel=true

I have tried with proxy value set to edge and passthrough.

Below is my nginx proxy configuration.

server {
    server_name   <admin-domain-name>;

    access_log  /var/log/nginx/keycloak-mgmt-access.log  main;
    error_log  /var/log/nginx/keycloak-mgmt-error.log;

    # ============= Proxy Configuration ============= #

    location / {
      proxy_pass_request_headers on;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_set_header X-Forwarded-Host $host;
      proxy_pass http://localhost:8080;
    }

    # ============= Proxy Configuration ============= #

    # //============ SSL Settings =============== //

}

server {
    server_name <domain-name>;

    access_log  /var/log/nginx/keycloak-access.log  main;
    error_log  /var/log/nginx/keycloak-error.log;

    # ============= Proxy Configuration ============= #

    location /realms/ {
      proxy_pass_request_headers on;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_set_header X-Forwarded-Host $host;
      proxy_pass http://localhost:8080;
    }

    location /resources/ {
      proxy_pass_request_headers on;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_set_header X-Forwarded-Host $host;
      proxy_pass http://localhost:8080;
    }

    # ============= Proxy Configuration ============= #

    # //============ SSL Settings =============== //

}

server {
    if ($host = <domain-name>) {
        return 301 https://$host$request_uri;
    }

    server_name <domain-name>;
    listen 80;
    return 404;


}server {
    if ($host = <admin-domain-name>) {
        return 301 https://$host$request_uri;
    } 
    server_name   <admin-domain-name>;
    listen 80;
    return 404;


}

Came across couple of old similar issues but that involved modifying the frontendUrl or updating the Web origin with + but it doesn’t seem to be relevant for or working for quarkus distributions.

Not sure what I’m missing. Any help would be much appreciated.