vui-ui: Not working at all

Helm values:

global:
  veleroNamespace: velero

uiIngress:
  enabled: true
  ingressClassName: nginx
  metadata:
    annotations: []
  spec:
    tls:
    - hosts:
      - velero-ui.domain.com
      secretName: velero-ui-tls

Result: Unable to login, login button not working

Error in web ui: image

❯ velero version Client: Version: v1.14.0 Git commit: none Server: Version: v1.14.0

velero ui: Helm release 0.1.12

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 21 (10 by maintainers)

Most upvoted comments

As mentioned earlier, from a technical standpoint it’s crucial that the Next.js frontend effectively communicates with the FastAPI backend. If the frontend in the browser cannot reach the API endpoints, the application will not function correctly. The frontend interacts directly with the backend API through HTTP requests (such as GET, POST, etc.).

It’s imperative that these API endpoints are accessible from the client’s browser. This requires proper exposure and configuration of the API endpoints to ensure that requests from the frontend can reach them and receive valid responses.

If you’re deploying with a domain, ensure it resolves to ingresses that route requests to the API. Alternatively, if using NodePort, ensure the APIs are exposed and reachable from client browsers.