Cant login to launch after downloading and installing

Cant login to launch after downloading and installing

Thanks for any help

Hello @robertcober! When you say you can’t log in, do you mean that you enter your username and password and getting an error? If so what is that error?

Also, can you grab a log for me to look at from here: C:\Users\<USERNAME>\.nvidia-omniverse\logs\launcher

Thanks Wendy! I got it to work by resetting my nvidia password

Hi I am also facing the same issue, how might I fix the install? I’ve tried uninstalling and reinstalling to no avail, it looks like I am missing auth.toml

Here is text from my log:

[2023-08-14 10:44:23.652] [info]  Omniverse Launcher 1.8.11 (production)
[2023-08-14 10:44:25.126] [info]  Argv: C:\Users\my-pc\AppData\Local\Programs\omniverse-launcher\NVIDIA Omniverse Launcher.exe
[2023-08-14 10:44:25.128] [info]  Crash dumps directory: C:\Users\my-pc\AppData\Roaming\omniverse-launcher\Crashpad
[2023-08-14 10:44:26.387] [error] Error happened during the update:  Error: net::ERR_CONNECTION_ABORTED
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:49549)
    at SimpleURLLoaderWrapper.emit (node:events:513:28)
[2023-08-14 10:44:27.447] [debug] Reset current installer.
[2023-08-14 10:44:27.583] [info]  Running production web server.
[2023-08-14 10:44:27.598] [info]  HTTP endpoints listening at http://localhost:33480
[2023-08-14 10:44:27.602] [debug] Sharing: false
[2023-08-14 10:44:27.626] [info]  Started the Navigator web server on 127.0.0.1:34080.
[2023-08-14 10:44:27.635] [error] (node:8232) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\my-pc\.nvidia-omniverse\config\auth.toml'
(Use `NVIDIA Omniverse Launcher --trace-warnings ...` to show where the warning was created)
[2023-08-14 10:44:27.635] [error] (node:8232) 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 https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
[2023-08-14 10:44:28.194] [info]  Can't access the C:\Users\my-pc\.nvidia-omniverse\config\privacy.toml file:  ENOENT: no such file or directory, access 'C:\Users\my-pc\.nvidia-omniverse\config\privacy.toml'
[2023-08-14 10:44:28.293] [info]  Can't access the C:\Users\my-pc\.nvidia-omniverse\config\privacy.toml file:  ENOENT: no such file or directory, access 'C:\Users\my-pc\.nvidia-omniverse\config\privacy.toml'
[2023-08-14 10:44:28.408] [info]  Failed to get GDPR, retrying in 2.5 seconds...
[2023-08-14 10:44:29.483] [info]  Registered omniverse-launcher for Windows.
[2023-08-14 10:44:29.484] [info]  Registered omniverse for Windows.
[2023-08-14 10:44:30.916] [info]  Failed to get GDPR, retrying in 2.5 seconds...
[2023-08-14 10:44:32.636] [error] (node:8232) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\my-pc\.nvidia-omniverse\config\auth.toml'
[2023-08-14 10:44:32.637] [error] (node:8232) 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 https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
[2023-08-14 10:44:33.425] [error] FetchError: request to https://messages.launcher.omniverse.nvidia.com/en/gdpr.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\my-pc\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:50236)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2023-08-14 10:44:33.425] [error] Error occurred in handler for 'data-sharing-load-gdpr': FetchError: request to https://messages.launcher.omniverse.nvidia.com/en/gdpr.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\my-pc\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:50236)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2023-08-14 10:44:34.438] [info]  Failed to get GDPR, retrying in 2.5 seconds...
[2023-08-14 10:44:36.954] [info]  Failed to get GDPR, retrying in 2.5 seconds...
[2023-08-14 10:44:37.638] [error] (node:8232) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\my-pc\.nvidia-omniverse\config\auth.toml'
[2023-08-14 10:44:37.639] [error] (node:8232) 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 https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
[2023-08-14 10:44:39.524] [error] FetchError: request to https://messages.launcher.omniverse.nvidia.com/en/gdpr.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\my-pc\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:50236)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2023-08-14 10:44:39.525] [error] Error occurred in handler for 'data-sharing-load-gdpr': FetchError: request to https://messages.launcher.omniverse.nvidia.com/en/gdpr.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\my-pc\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:50236)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2023-08-14 10:44:41.546] [info]  Failed to get GDPR, retrying in 2.5 seconds...
[2023-08-14 10:44:42.640] [error] (node:8232) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\my-pc\.nvidia-omniverse\config\auth.toml'
[2023-08-14 10:44:42.641] [error] (node:8232) 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 https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
[2023-08-14 10:44:44.057] [info]  Failed to get GDPR, retrying in 2.5 seconds...
[2023-08-14 10:44:46.092] [info]  Login URL opened.
[2023-08-14 10:44:46.163] [info]  Waiting for login result...
[2023-08-14 10:44:46.565] [error] FetchError: request to https://messages.launcher.omniverse.nvidia.com/en/gdpr.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\my-pc\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:50236)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2023-08-14 10:44:46.565] [error] Error occurred in handler for 'data-sharing-load-gdpr': FetchError: request to https://messages.launcher.omniverse.nvidia.com/en/gdpr.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\my-pc\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:50236)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2023-08-14 10:44:47.642] [error] (node:8232) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\my-pc\.nvidia-omniverse\config\auth.toml'
[2023-08-14 10:44:47.642] [error] (node:8232) 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 https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8)
[2023-08-14 10:44:50.576] [info]  Failed to get GDPR, retrying in 2.5 seconds...
[2023-08-14 10:44:52.644] [error] (node:8232) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\my-pc\.nvidia-omniverse\config\auth.toml'
[2023-08-14 10:44:52.644] [error] (node:8232) 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 https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)
[2023-08-14 10:44:53.086] [info]  Failed to get GDPR, retrying in 2.5 seconds...
[2023-08-14 10:44:55.596] [error] FetchError: request to https://messages.launcher.omniverse.nvidia.com/en/gdpr.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\my-pc\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:50236)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2023-08-14 10:44:55.597] [error] Error occurred in handler for 'data-sharing-load-gdpr': FetchError: request to https://messages.launcher.omniverse.nvidia.com/en/gdpr.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\my-pc\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:50236)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2023-08-14 10:44:56.196] [info]  WEB /login-result?ui_locales=en&code=MKsToRoG5J1L0Ol2A9oi0RhZdS0CSmi_UA2zUZ9FLZVBIbOFvADwBA5rJ6DyD0-uWW-lB0S_TV_G6Er1Cebtxg
[2023-08-14 10:44:57.645] [error] (node:8232) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\my-pc\.nvidia-omniverse\config\auth.toml'
[2023-08-14 10:44:57.645] [error] (node:8232) 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 https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 11)
[2023-08-14 10:45:01.162] [info]  Received login result.
[2023-08-14 10:45:01.184] [info]  Can't access the C:\Users\my-pc\.nvidia-omniverse\config\privacy.toml file:  ENOENT: no such file or directory, access 'C:\Users\my-pc\.nvidia-omniverse\config\privacy.toml'
[2023-08-14 10:45:02.646] [error] (node:8232) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\my-pc\.nvidia-omniverse\config\auth.toml'
[2023-08-14 10:45:02.647] [error] (node:8232) 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 https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 12)

I just used the standard installer, initally was able to install and run initially. But I wanted to reconfigure my install directories, after uninstalling, and reinstalling, Omniverse Launcher, pops up the Auth in my browser, after entering my pw, launcher never passes the login screen. I’ve tried resetting the pw as well. Seems like the install is broken, and something is persistent on the system after uninstalling, so I never get a true clean re-install.

based on the log, it seems like OV is having trouble accessing both auth.toml and privacy.toml. another issue pertains to not being able to retrieve GDPR, which could be related a drop of your connection. are you on VPN/wifi or anything specific? when you say “never passes the login screen”, are you seeing the loading icon after hitting log in?

speaking of setups, can you mention your hardware specs? (asking not because it 100% has to do with your problem, but just trying to solicit information for when the devs come across this thread)

when you were uninstalling, did you use the Cleanup Tool at all?

Unfortunately the cleanup tool didn’t work, same behavior. I’ve tried logging in with and without my vpn running, same result. pasted in an image from the browser, when Launcher pops up the password screen. It looks like, the server isn’t responding.

I notice the cleanup tool says:

This will not remove any Data that has been saved in Nucleus,
the Data folder is preserved.

I’ll see if I can find that and delete it, to see if it’s not the cause of the issue.

image

the full flow that fails currently is:

  • I run Launcher and enter my email address
  • The browser pops up a password prompt, Launcher has a spinning progress wheel.
  • I Enter the password, and it , Says: “You can continue to work in the application.”
  • Pops up a confirm dialog, asking to: “Open NVIDIA Omniverse Launcher”
  • I click “Open NVIDIA Omniverse Launcher”
  • Focus returns to Launcher, the loading wheel spins for a second or 2, then stops.
  • Launcher doesn’t get past the login screen

is it possible for you to post the full Launcher log instead of just a snippet?

when you reinstalled it the first time around, did you install as admin? there are also TCP/IP and port config you will want to consider.

Hello @WendyGram I have some similler question about auyh.toml file loss, could you help me?

I see the same question on another thread about this. You have also lost or corrupted your “auth.toml” file ?

I creat a blank auth.toml file by my self, and it didn’t jump out the error lines, thanks for your reply.
but i don’t know I made the file by myself might cause some other errors?

Launcher 1.9.8 has been released !!