Is this page helpful?

Troubleshooting and FAQs#

_images/ov_cloud_banner.jpg

Overview#

This page provides troubleshooting tips and frequently asked questions and answers. For additional support, access the NVIDIA Enterprise Support Portal here.

What are the supported platforms & web browsers for streaming?

Omniverse on DGX Cloud supports the following platforms & web browsers:

Browser

Windows

Linux

macOS

Chromium-based browsers

Yes

Yes

Yes

Mozilla Firefox

Yes

Yes

Yes

Safari

N/A

N/A

Yes

Note

Omniverse on DGX Cloud supports most Chromium-based browsers including Google Chrome and Microsoft Edge.

How do I check if the NVCF services are up and functional?

NVCF provides an API endpoint to verify services. The endpoint to query is https://api.nvcf.nvidia.com/health.

Is there a pre-built validation container for testing streaming functionality?

Yes; a streaming validation container is available on NGC here. To use this container, follow these steps using a Linux-based workstation:

  1. Download the streaming validation container from NGC using the link above.

  2. Upload that container to the Private Registry within your NGC Org and deploy it as a function using these instructions.

  3. If you are using the Portal Sample, publish the function and execute it using these instructions.

  4. The following image should appear streaming from your tenant:

_images/validation_container.jpg

Note

When using this container, ensure you are using the correct health and inference endoints as specified on the NGC Overview or the deployment will not successfully complete.

How do I change the OIDC claim name carrying the information of the admin group?

  1. Change “groups” to “<your claim name>” in two lines of code:

_images/oidc_claim_name.jpg

Note

The claim is expected to hold a JSON array; using a single value might not be supported.

Why am I receiving “401 Unauthorized” entries in the backend logs?
_images/unauthorized_errors.jpg

It is likely the backend cannot reach the OIDC endpoints specified in the configuration file, particularly the JWKS and Userinfo endpoints. Verify connectivity from the backend host or container to these endpoints using the following command:

curl '*'<an OIDC API endpoint you have in your settings.toml>

Note

If your environment includes proxy servers that could block communication between the portal and OIDC endpoints, ensure the appropriate environment variables are set persistently.

export http_proxy=<your HTTP proxy>
export https_proxy=<your HTTPS proxy>
export HTTP_PROXY=<your HTTP proxy>
export HTTPS_PROXY=<your HTTPS proxy>
export NO_PROXY=<your list of URLs that don't need proxying>

This can also be caused by a misconfiguration in your settings.toml file on the backend. This prevents the backend service from successfully authenticating your account with your identity provider (IDP) to retrieve the list of available applications.

If the GET request to the /apps API endpoint fails, an ‘Unauthorized’ error message will be returned.

This occurs when a user has not signed in through the web frontend, which is required to access the Swagger UI.

The published Apps disappeared from the Portal! What happened?

A common reason for published Apps to disappear from the Portal is due to the expiry of the NGC API Key used. To resolve this issue, generate a new API Key within NGC and replace the one the Portal is using within its configuration.

For information on generating NGC API Keys, click here to access the NGC documentation.

On this page