Skip to content

Browser UI 'Not Secure' Message

This guide addresses the "not secure" warning message experienced when accessing the GPU Cluster Manager Browser User Interface (BUI).

Problem Summary

Issue: After installing MemVerge AI GPU Cluster Manager, the browser shows the URL as "not secure" when accessing the BUI. Example of Error Message in Browser UI:

Not Secure Error Message

Affected: GPU Cluster Manager.

Cause: There are two possible causes:

  1. If installed with a Self-Signed Certificate, this is expected as browsers do not inherently trust self-signed certificates.

  2. If installed with Let's Encrypt or Bring Your Own Certificate, the Kubernetes Certificate Manager may need time (minutes to hours) to complete the authentication and certificate issuance process.

Error Message: Browser displays a "not secure" warning in the URL bar.

Investigation Steps

  1. Check Installation Method: Determine which certificate method was used during installation. This can usually be found by reviewing your installation logs or the configuration used.

    Example Command(may vary based on installation specifics): 

    # grep "certificate-method" /path/to/install/logs

    Expected Output: Confirm if "Self-Signed Certificate," "Let's Encrypt," or "Bring Your Own Certificate" method was used.

  2. Check Time Elapsed (for Let's Encrypt/Bring Your Own Certificate): Note how long it has been since the GPU Cluster Manager was installed or since the last certificate renewal attempt.

    Example Commands: 

    # kubectl get cert -n <namespace> -o yaml | grep creationTimestamp
# kubectl get challengerequest -n <namespace> -o yaml | grep creationTimestamp

    Expected Output: Determine if sufficient time (e.g., several hours) has passed for certificate issuance.

Resolution Steps

Prerequisites: Understand that the BUI is fully operational despite the warning.

Apply Fix:

  • If using Self-Signed Certificate: This warning is expected and can be safely ignored. There is no fix to remove the warning without replacing the self-signed certificate with a trusted one.
  • If using Let's Encrypt or Bring Your Own Certificate: Wait for at least 24 hours from the installation time. The Certificate Manager often requires time to sync and finalize the certificate.

Verify Fix:

  • After Waiting (Let's Encrypt/Bring Your Own Certificate), Re-access the BUI in your browser

Expected Output: The browser should now show the URL as secure (e.g., a padlock icon), indicating the trusted certificate has been deployed and recognized.

Further Assistance: If the problem persists after 24 hours (for Let's Encrypt or Bring Your Own Certificate installations), further investigation is required. Contact MemVerge Support for advanced troubleshooting.