SDKMANAGER session expired please log in again

Hello, for the past week I’ve been unable to login in the sdk manager due to persistently failing the final steps of the login process (login the account in the browser, wait for verification, close browser). I’ve also tested with QR code but it immediately fails once it starts. I’ve checked the logs and seems to be related to a self signed certificate, any help about fixing this issue?

So far I uninstalled/installed sdk, cleared the cache and configuration and no success.

*** Please note that this reply is generated by LLM automatically ***

I understand that you’re experiencing issues with logging in to the SDK Manager, specifically with the final steps of the login process. You’ve tried various troubleshooting steps, including uninstalling and reinstalling the SDK, clearing the cache and configuration, but to no avail. You’ve also checked the logs, which suggest that the issue is related to a self-signed certificate.

Before we dive into potential solutions, I’d like to clarify a few things:

  1. SDK Manager: The SDK Manager is a tool used to manage and configure NVIDIA SDKs, including the Jetson SDK.
  2. Self-signed certificate: A self-signed certificate is a certificate that is not issued by a trusted Certificate Authority (CA), but rather by the entity itself. This can cause issues with authentication and verification.

To help you resolve this issue, I’ll provide a few potential solutions:

Solution 1: Update the SDK Manager

Ensure that you’re running the latest version of the SDK Manager. You can check for updates by launching the SDK Manager and looking for any available updates.

Solution 2: Configure the SDK Manager to trust self-signed certificates

You can try configuring the SDK Manager to trust self-signed certificates. This can be done by adding the following flag to the SDK Manager’s configuration file:

--ignore-certificate-errors

This flag will allow the SDK Manager to ignore certificate errors, including those related to self-signed certificates.

Solution 3: Use a trusted Certificate Authority (CA)

If possible, consider using a trusted Certificate Authority (CA) to issue a certificate for your SDK Manager. This will ensure that the certificate is trusted by the SDK Manager and will not cause any authentication issues.

Solution 4: Disable certificate verification

As a last resort, you can try disabling certificate verification in the SDK Manager. This can be done by adding the following flag to the SDK Manager’s configuration file:

--disable-certificate-verification

Please note that disabling certificate verification can pose a security risk, as it allows the SDK Manager to connect to untrusted servers.

Comparison with other platforms

It’s worth noting that the issue you’re experiencing is specific to the SDK Manager and is not related to other platforms, such as GitHub or Jenkins. However, if you’re experiencing similar issues with other platforms, it may be worth investigating whether the issue is related to a self-signed certificate or another authentication issue.

Additional troubleshooting steps

If none of the above solutions work, you can try the following additional troubleshooting steps:

  • Check the SDK Manager’s logs for any error messages related to certificate verification.
  • Verify that the SDK Manager is configured correctly and that the certificate is properly installed.
  • Try using a different browser or authentication method to see if the issue persists.

I hope this helps! If you have any further questions or concerns, please don’t hesitate to ask.

Hi,

One question to confirm:

  • Is your ubuntu a native or a virtual machine?

Thanks

Using Ubuntu 20.04 in a native machine and tried login with firefox and chrome browsers
Adding the following:
–disable-certificate-verification
–ignore-certificate-errors

Didn’t seem to work. I’ll try to see if maybe I can fix with configuring SDK manager (I was using default settings which didn’t created this issue until now for some reason)

Hi,

Please confirm whether hosts behind firewalls, proxies, or VPNs.
If yes, please disable to check if issue exists.

Thanks

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.