Skip to main content
Version: 2.5

Configure access to UI

If the standard Portworx Central UI endpoint configuration does not meet your requirements, you can configure access using HTTPS, access it through the load balancer, or even navigate to one of your node IPs directly.

Access Portworx Central user interface using node IP

You can access Portworx Central by directly navigating to one of your node's IP addresses.

  1. Find the public/external IP (NODE_IP) of any node in your current Kubernetes cluster.

  2. Find the node port (NODE_PORT) of the px-central-ui service.

Once you have found the node IP and port, you can combine them to access the Portworx Backup UI:

http://NODE_IP:NODE_PORT

Additionally, you can access the Keycloak UI at the /auth path:

http://NODE_IP:NODE_PORT/auth
note

You can access Portworx Central user interface with node IP in both internet-connected and air-gapped environments.

Access Portworx Central UI using DNS over HTTPS

note

Make sure that all the associated pods can resolve the DNS name.

To access Portworx Central user interface as a user from a cluster with load balancer and self-signed certificates installed over HTTPS, perform the following steps:

  1. From the command prompt, navigate to the cluster where your Portworx Central is installed.

  2. Edit the keycloak sts:

  kubectl edit sts pxcentral-keycloak -n <px-central-installed-namespace> 
  1. Append this new key in env section:
- name: KC_HOSTNAME 
value: <px-central-ui-host-name>
  1. Set the following key values to true:

  • name: KC_HOSTNAME_STRICT value: "true"
  • name: KC_HOSTNAME_STRICT_HTTPS value: "true"

Access Portworx Central UI over HTTP

To access Portworx Central user interface over HTTP:

  1. From the command prompt, navigate to the cluster where your Portworx Central is installed.

  2. Edit the keycloak sts:

    kubectl edit sts pxcentral-keycloak -n <px-central-installed-namespace>
  3. Append this new key in env section:

- name: KC_HTTP_ENABLED
value: `true`
  1. Delete the following key in env section:
- name: KC_PROXY 
value: edge
Was this page helpful?