Hello!
I want to run isaac sim using omniverse launcher. However, when I download the omniverse launcher and run the AppImage format file, I get the following image error:
I think that it will be solved if you specify a proxy or firewall, but I do not know where to write it. Could anyone please tell me?
Thanks you.
Hi @mri_y , Thanks for your post and your interest in the Omniverse,
The following below endpoints need to be accessible for Omniverse Functionality
Alternatively, you can whitelist https://*.nvidia.com in your firewall
The following details are provided in the below document
https://docs.omniverse.nvidia.com/prod_launcher/prod_launcher/firewalls.html
Thank you for your reply!
When I made a wildcard entry on the firewall with https: //*.nvidia.com, the image error disappeared, but the following log-like error is displayed on the terminal and I cannot proceed.
[Desktop Entry]
Name=omniverse-launcher
Exec=/home/user/omniverse-launcher-linux.AppImage --no-sandbox %u
Type=Application
Terminal=false
MimeType=x-scheme-handler/omniverse
[2021-06-22 16:08:42.054] [error] Failed to register a custom protocol handler for omniverse: Error: Command failed: xdg-desktop-menu install /tmp/om niverse-launcher-npBuXB/omniverse.desktop
xdg-desktop-menu: filename 'omniverse.desktop' does not have a proper vendor prefix
A vendor prefix consists of alpha characters ([a-zA-Z]) and is terminated
with a dash ("-"). An example filename is 'example-omniverse.desktop'
Use --novendor to override or 'xdg-desktop-menu --manual' for additional info.
at ChildProcess.exithandler (child_process.js:312:12)
at ChildProcess.emit (events.js:315:20)
at maybeClose (internal/child_process.js:1021:16)
at Socket.<anonymous> (internal/child_process.js:443:11)
at Socket.emit (events.js:315:20)
at Pipe.<anonymous> (net.js:674:12)
[2021-06-22 16:10:49.891] [error] FetchError: request to https://messages.launcher.omniverse.nvidia.com/gdpr.json failed, reason: connect ETIMEDOUT 13 .227.49.28:443
at ClientRequest.<anonymous> (/tmp/.mount_omniveT6cUV6/resources/app.asar/dist/main.js:344:26839)
at ClientRequest.emit (events.js:315:20)
at TLSSocket.socketErrorListener (_http_client.js:426:9)
at TLSSocket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
[2021-06-22 16:10:49.891] [error] Error occurred in handler for 'data-sharing-agreement': FetchError: request to https://messages.launcher.omniverse.n vidia.com/gdpr.json failed, reason: connect ETIMEDOUT 13.227.49.28:443
at ClientRequest.<anonymous> (/tmp/.mount_omniveT6cUV6/resources/app.asar/dist/main.js:344:26839)
at ClientRequest.emit (events.js:315:20)
at TLSSocket.socketErrorListener (_http_client.js:426:9)
at TLSSocket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
[2021-06-22 16:10:49.894] [error] FetchError: request to https://messages.launcher.omniverse.nvidia.com/gdpr.json failed, reason: connect ETIMEDOUT 13 .227.49.28:443
Is this because nvidia communication is failing?
Since it says ETIMEDOUT, I think it is a connection error. Maybe the registration method for https: //*.nvidia.com is wrong. Also, the proxy may be blocking the move to the browser. If possible, could you please tell me where to register the proxy and firewall when launching omniverse-launcher?
The OS used is Linux Ubuntu 18.04.
Thank you.
Hi @mri_y , Thanks for your reply and your interest in Omniverse, My apologies for my delayed response, I have checked with other teams, it seems the exact issue is the machine at your end is unable access our server to download the latest GDPR agreement
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
