nginx /hyperdx subpath

I get 404. What did I wrong?

compose.yaml

  hyperdx:
    image: docker.hyperdx.io/hyperdx/hyperdx-all-in-one
    container_name: hyperdx-ui
    depends_on:
      - clickhouse
      - otel-collector
    environment:
      - HYPERDX_API_URL=${HYPERDX_API_URL}
      - HYPERDX_API_PORT=${HYPERDX_API_PORT}
      - HYPERDX_APP_URL=${HYPERDX_APP_URL}
      - HYPERDX_APP_PORT=${HYPERDX_APP_PORT}
      - FRONTEND_URL=${FRONTEND_URL}
      - HYPERDX_BASE_PATH=${HYPERDX_BASE_PATH}
      - NEXT_PUBLIC_HYPERDX_BASE_PATH=${NEXT_PUBLIC_HYPERDX_BASE_PATH}

      - TZ=Europe/Moscow
    volumes:
      - ./volumes/hyperdx/data:/data/db
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    networks:
      - schedule_net
    logging:
      driver: "json-file"
      options:
        max-size: "10m"
        max-file: 1

.env

  HYPERDX_API_URL=https://schedule-imsit.ru
  HYPERDX_API_PORT=8000
  HYPERDX_APP_URL=https://schedule-imsit.ru
  HYPERDX_APP_PORT=8081
  FRONTEND_URL=https://schedule-imsit.ru/hyperdx
  HYPERDX_BASE_PATH=/hyperdx
  NEXT_PUBLIC_HYPERDX_BASE_PATH=/hyperdx

nginx.conf

  location /hyperdx/ {
              limit_req zone=req_limit_per_ip burst=10 nodelay;
  
              proxy_pass http://hyperdx-ui:8081/;
  
              proxy_set_header Host $host;
              proxy_set_header X-Real-IP $remote_addr;
              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_set_header Authorization $http_authorization;
  
              proxy_set_header Upgrade $http_upgrade;
              proxy_set_header Connection $connection_upgrade;
  
              proxy_buffering off;
   }

Originally posted by @simadimonyan in https://github.com/hyperdxio/hyperdx/issues/1188#issuecomment-3690558651

Start with compose.yaml, the .env values, and the nginx.conf location block, then reproduce the 404 through the /hyperdx subpath. Compare the configured base paths, frontend URL, ports, and proxy routing to determine where the request stops. Done means the HyperDX interface is reachable through the documented subpath without 404 responses.