Can not install anything

i’m working on behind company proxy.
in omniverse-launcher, login and news page shows up ok.
but when ever i try to install anything following error show up.

17:11:06.961 › FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET

17:11:06.962 › Error occurred in handler for ‘prepare-install’: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET

if i copy & paste those urls to at the same pc’s chrome browser, json file successfully downloads without any problem.
i tried launcher-cleanup but same problem.

does anyone can help ?

1 Like

Hello @user93548! I will need a full log to see if I can figure out where the problem might be happening. Can you send me the following information?

  • Operating System
  • GPU / GPU Driver
  • Full logs from: C:\Users\<USERNAME>\.nvidia-omniverse\logs\launcher

hi, below is full log.
many thanks.

cat launcher.log

[2022-04-21 10:18:05.481] [info] Omniverse Launcher 1.5.2 (production)
[2022-04-21 10:18:05.485] [info] Argv: /tmp/.mount_omniveVnhHvt/omniverse-launcher
[2022-04-21 10:18:05.585] [debug] Running “/work/nvidia/omniverse-launcher/share/ov/pkg/cache-2022.1.0/System Monitor/omni-system-monitor”
[2022-04-21 10:18:05.591] [debug] Reset current installer.
[2022-04-21 10:18:05.684] [error] (node:8494) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron. See [Discussion] Changing the defaults for nodeIntegration and contextIsolation to improve the default security posture of Electron applications · Issue #23506 · electron/electron · GitHub for more information
[2022-04-21 10:18:06.053] [info] Requesting the feature list for en…
[2022-04-21 10:18:06.072] [info] Logged in.
[2022-04-21 10:18:06.080] [info] Enabled features for en: { bugReports: false }
[2022-04-21 10:18:06.104] [info] Running production web server.
[2022-04-21 10:18:06.106] [info] HTTP endpoints listening at http://localhost:33480
[2022-04-21 10:18:06.107] [info] Saving omniverse-launcher.desktop file to /tmp/omniverse-launcher-nT67jr…
[2022-04-21 10:18:06.107] [debug]
[Desktop Entry]
Name=omniverse-launcher
Exec=“/work/nvidia/omniverse-launcher-linux.AppImage” --no-sandbox %u
Type=Application
Terminal=false
MimeType=x-scheme-handler/omniverse-launcher
[2022-04-21 10:18:06.158] [info] Saving omniverse.desktop file to /tmp/omniverse-launcher-Y2iGav…
[2022-04-21 10:18:06.159] [debug]
[Desktop Entry]
Name=omniverse-launcher
Exec=“/work/nvidia/omniverse-launcher-linux.AppImage” --no-sandbox %u
Type=Application
Terminal=false
MimeType=x-scheme-handler/omniverse
[2022-04-21 10:18:06.203] [error] (node:8494) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, unlink ‘/home/robotbiz/.config/autostart/nvidia-omniverse-launcher.desktop’
[2022-04-21 10:18:06.203] [error] (node:8494) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see Command-line API | Node.js v18.9.0 Documentation). (rejection id: 1)
[2022-04-21 10:18:06.203] [error] (node:8494) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[2022-04-21 10:18:06.238] [error] (node:8494) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron. See [Discussion] Changing the defaults for nodeIntegration and contextIsolation to improve the default security posture of Electron applications · Issue #23506 · electron/electron · GitHub for more information
[2022-04-21 10:18:37.862] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
at ClientRequest. (/tmp/.mount_omniveVnhHvt/resources/app.asar/dist/main.js:38:29211)
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)
[2022-04-21 10:18:37.863] [error] Error occurred in handler for ‘prepare-install’: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
at ClientRequest. (/tmp/.mount_omniveVnhHvt/resources/app.asar/dist/main.js:38:29211)
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)