I cannot log in SDK MANAGER

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”):
Software Version
other

Target Operating System
Linux

Hardware Platform
other

SDK Manager Version
1.5.0.7774

Host Machine Version
native Ubuntu 16.04.6 LTS

Hello

My problem is that I can’t log in to the SDK manager.
I’m trying to launch the SDK manager, select the NVIDIA DEVELOPER tab and log in.
I have logged in to my NVIDIA account in my browser.
However, when I try to log in with the NVIDIA SDK MANAGER, the login gauge stops halfway and the login is not completed.

Follow the manual on the following page.
https://docs.nvidia.com/sdk-manager/download-run-sdkm/index.html

What is the problem?

2

What’s the platform you’re using?
Are you the member of the the NVIDIA DRIVE Developer Program for DRIVE AGX?

4

I will use NVIDIA DRIVE Developer Program for DRIVE AGX
and I am already a member of the NVIDIA DRIVE Developer Program for DRIVE AGX

5

Hi @hiroki.omatsu.df

Where does it stop? Could you share a screenshot?
Could you share ~/.nvsdkm directory for our checking? Thanks.

6

Here is screenshot.

Screenshot from 2021-06-03 08-55-20
Screenshot from 2021-06-03 08-55-20700×591 177 KB

and, nvsdkm directory is here.
replays sdkm-2021-06-02-16-11-43.log sdkm.db
sdkm-2021-06-02-14-29-03.log sdkm-2021-06-02-16-45-23.log sdkm.log
sdkm-2021-06-02-14-43-30.log sdkm-2021-06-03-08-50-58.log

7

Dear @hiroki.omatsu.df,
It opens a new web browser to enter credentials to complete the login process. Did you notice it? Have you entered the credentials in web browser?

8

I know

Screenshot from 2021-06-03 13-45-23
Screenshot from 2021-06-03 13-45-23949×659 576 KB

But
I got error message “failed to get client token”

Screenshot from 2021-06-03 13-46-01
Screenshot from 2021-06-03 13-46-01798×601 84.6 KB

9

Dear @hiroki.omatsu.df,
Is the sdkmanager version 1.5.07774? Please confirm if you see “Failed to get client token” error consistently after successfully login via web browser?

10

sdkmanager version is 1.5.0-7774

First I click Login at SDK manager.
Next, log in to my account with web browser.
Finally I was able to confirm error “Failed to get client token”.

11

Please upload the logs. Thanks.

12

This is the latest log

16:21:54.789 - info: SDK Manager started running at: 2021-06-04 16:21:54.786
16:21:54.793 - info: SDK Manager log file name: sdkm-2021-06-04-16-21-54.log
16:21:54.794 - info: SDK Manager client version: 1.5.0
16:21:54.795 - info: SDK Manager is running in GUI mode
16:21:58.458 - info: Current DB Version: 14
16:22:00.024 - warn: Registering a callback with no name for event: System sett$
16:22:00.477 - info: User agent for http requests: SDKM/1.5.0.7774 (ubuntu1604)
16:22:00.587 - warn: Registering a callback with no name for event: Session sta$
16:22:00.876 - warn: Registering a callback with no name for event: Session sta$
16:22:00.877 - warn: Registering a callback with no name for event: Report comp$
16:22:00.877 - warn: Registering a callback with no name for event: Report comp$
16:22:00.879 - info: downloadMetrics.reset
16:22:00.879 - warn: Registering a callback with no name for event: Session sta$
16:22:00.879 - warn: Registering a callback with no name for event: Session res$
16:22:00.880 - warn: Registering a callback with no name for event: Session sta$
16:22:00.880 - warn: Registering a callback with no name for event: Session end$
16:22:00.881 - warn: Registering a callback with no name for event: File init d$
16:22:00.881 - warn: Registering a callback with no name for event: File pendin$
16:22:00.881 - warn: Registering a callback with no name for event: File starte$
16:22:00.881 - warn: Registering a callback with no name for event: File finish$
16:22:00.881 - warn: Registering a callback with no name for event: File checks$
16:22:00.881 - warn: Registering a callback with no name for event: Component i$
16:22:00.882 - warn: Registering a callback with no name for event: Component s$
16:22:00.882 - warn: Registering a callback with no name for event: Component f$
16:22:00.882 - warn: Registering a callback with no name for event: Component f$
16:22:00.882 - warn: Registering a callback with no name for event: Component f$
16:22:00.883 - warn: Registering a callback with no name for event: Session sta$
16:22:00.883 - warn: Registering a callback with no name for event: Component f$
16:22:00.894 - warn: Registering a callback with no name for event: Active bund$
16:22:00.894 - warn: Registering a callback with no name for event: Component f$
16:22:00.896 - info: Forking worker process
16:22:00.912 - info: Initializing the download service
16:22:00.930 - info: Download service pid is: 2687
16:22:00.942 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:22:00.946 - warn: Registering a callback with no name for event: File downlo$
16:22:00.946 - warn: Registering a callback with no name for event: File finish$
16:22:00.948 - warn: Registering a callback with no name for event: Session sta$
16:22:00.948 - warn: Registering a callback with no name for event: File downlo$
16:22:00.948 - warn: Registering a callback with no name for event: File finish$
16:22:00.948 - warn: Registering a callback with no name for event: File reset $
16:22:00.949 - warn: Registering a callback with no name for event: File downlo$
16:22:00.949 - warn: Registering a callback with no name for event: Component i$
16:22:00.949 - warn: Registering a callback with no name for event: Component s$
16:22:00.949 - warn: Registering a callback with no name for event: Component p$
16:22:00.949 - warn: Registering a callback with no name for event: Component f$
16:22:00.952 - info: Download manager can use up to 16 download threads per file
16:22:00.952 - warn: Registering a callback with no name for event: Session sta$
16:22:01.015 - info: create .sdkm.bashrc under /home/Hidden/.nvsdkm/.sdkm.bashrc
16:22:01.023 - info: installMetrics.reset
16:22:01.023 - warn: Registering a callback with no name for event: Session sta$
16:22:01.023 - info: uninstallMetrics.reset
16:22:01.023 - warn: Registering a callback with no name for event: Active bund$
16:22:01.024 - warn: Registering a callback with no name for event: Active bund$
16:22:01.025 - warn: Registering a callback with no name for event: Component f$
16:22:01.025 - warn: Registering a callback with no name for event: File finish$
16:22:01.025 - warn: Registering a callback with no name for event: Component f$
16:22:01.025 - warn: Registering a callback with no name for event: Session sta$
16:22:01.025 - warn: Registering a callback with no name for event: Session res$
16:22:01.025 - warn: Registering a callback with no name for event: Session pau$
16:22:01.025 - warn: Registering a callback with no name for event: Session com$
16:22:02.545 - warn: Registering a callback with no name for event: File starte$
16:22:02.545 - warn: Registering a callback with no name for event: File downlo$
16:22:02.545 - warn: Registering a callback with no name for event: File checks$
16:22:02.545 - warn: Registering a callback with no name for event: File finish$
16:22:02.808 - warn: Registering a callback with no name for event: Active bund$
16:22:02.813 - warn: Registering a callback with no name for event: Terminal ou$
16:22:02.813 - warn: Registering a callback with no name for event: Login progr$
16:22:02.813 - warn: Registering a callback with no name for event: undefined
16:22:02.813 - warn: Registering a callback with no name for event: Component d$
16:22:02.813 - warn: Registering a callback with no name for event: Component p$
16:22:02.813 - warn: Registering a callback with no name for event: Component s$
16:22:02.813 - warn: Registering a callback with no name for event: File starte$
16:22:02.813 - warn: Registering a callback with no name for event: Component i$
16:22:02.814 - warn: Registering a callback with no name for event: Component f$
16:22:02.814 - warn: Registering a callback with no name for event: Component f$
16:22:02.814 - warn: Registering a callback with no name for event: Component f$
16:22:02.814 - warn: Registering a callback with no name for event: Group finis$
16:22:02.814 - warn: Registering a callback with no name for event: Component f$
16:22:02.814 - warn: Registering a callback with no name for event: Session pau$
16:22:02.814 - warn: Registering a callback with no name for event: Session res$
16:22:02.819 - info: Logger level is set to: info
16:22:03.108 - warn: Registering a callback with no name for event: Login progr$
16:22:03.108 - warn: Registering a callback with no name for event: CLI Abort
16:22:03.224 - info: Front-end main function (startMain) was called
16:22:03.318 - info: Creating auto update task
16:22:03.339 - info: Host OS: ubuntu1604
16:22:03.341 - info: packageJson: /opt/nvidia/sdkmanager/resources/app/package.$
16:22:03.363 - info: [Download Service]:Download service is initializing
Download service was initialized
Got heartbeat request

16:22:03.364 - info: [Download Service] Download service is alive
16:22:03.727 - info: Application configuration is:
{
mainRepoURL: 'https://developer.download.nvidia.com/sdkmanager/sdkm-config/ma$
PIDServer: ‘P’,
DevZoneServer: ‘P’,
}
16:22:03.922 - info: manifest: {“name”:“sdkmanager”,“releaseVersion”:“1.5.0”,"r$
16:22:03.922 - info: Telemetry parameters are: title: SDK Manager 1.5.0.7774 ve$
16:22:03.922 - info: autoLogin failed: Aborting auto login since there is no lo$
16:22:03.922 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:22:03.923 - info: Telemetry: allow = . isGDPRAllowed=false
16:22:03.929 - info: mainRepoUrl: https://developer.download.nvidia.com/sdkmana$
16:22:03.930 - info: logging in with l1 url: https://developer.download.nvidia.$
16:22:04.053 - info: Create timing task for auto update successfully.
16:22:07.588 - info: logging in to starfleet server
16:22:07.589 - info: Logging in with starfleet login method…
16:22:07.606 - info: Event: Login Progress: undefined
16:22:09.205 - info: Listening to Starfleet Redirect URL on port: 8080
16:22:09.207 - info: Listening to Starfleet Development signin URL on port: 396$
16:22:09.207 - info: Openning login URL in browser: https://login.nvidia.com/a$
16:22:09.216 - info: Event: Login Progress: Waiting for user to complete login $
16:25:18.781 - info: Got Starfleet server signin response. Request URL: /?ui_l$
16:25:18.782 - info: Event: Login Progress: Authenticating with NVIDIA server…
16:25:18.783 - info: Event: Login Progress: Login credentials retrieved success$
16:25:18.789 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:25:18.789 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:25:20.111 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:25:20.161 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:25:22.170 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:25:22.177 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:25:22.187 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:25:22.187 - error: Failed to get user information from Starfleet. Error: Req$
16:25:22.188 - info: Event: Login Complete: failed
16:25:22.188 - error: loginManager.login failed: Failed to get client token
16:42:38.341 - info: logging in to starfleet server
16:42:38.341 - info: Logging in with starfleet login method…
16:42:38.347 - info: Event: Login Progress: undefined
16:42:38.351 - info: Listening to Starfleet Development signin URL on port: 468$
16:42:38.351 - info: Openning login URL in browser: https://login.nvidia.com/a$
16:42:38.353 - info: Event: Login Progress: Waiting for user to complete login $
16:42:59.239 - info: Got Starfleet server signin response. Request URL: /?ui_l$
16:42:59.239 - info: Event: Login Progress: Authenticating with NVIDIA server…
16:42:59.240 - info: Event: Login Progress: Login credentials retrieved success$
16:42:59.243 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:42:59.243 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:43:00.333 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:43:00.338 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:43:02.386 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:43:02.402 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
16:43:02.402 - error: Failed to get user information from Starfleet. Error: Req$
16:43:02.409 - info: Event: Login Complete: failed
16:43:02.410 - error: loginManager.login failed: Failed to get client token
16:43:02.412 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$

thanks

13

I just noticed that you don’t use Ubuntu 18.04. Recent releases only support 18.04. You can check “System Requirements” document of the release you intend to install (System Requirements is for DRIVE OS 5.2.0). You may need to try on 18.04.

Which version are you trying to install?

14

Dear @hiroki.omatsu.df,
We have enquired internally about the issue. It seems login should work from ubuntu 16.04 as well. I notice some network proxy related issue in the log. Are you using any proxy settings?
Could you share complete sdkm.log to get more insights.

15

I am trying to install NVIDIA SDK Manager 1.5.1
And, I am using proxy setting correctly

16

This is sdkm.log

13:19:39.388 - info: SDK Manager started running at: 2021-06-07 13:19:39.385
13:19:39.390 - info: SDK Manager log file name: sdkm-2021-06-07-13-19-39.log
13:19:39.391 - info: SDK Manager client version: 1.5.0
13:19:39.392 - info: SDK Manager is running in GUI mode
13:19:42.021 - info: Current DB Version: 14
13:19:43.542 - warn: Registering a callback with no name for event: System sett$
13:19:43.968 - info: User agent for http requests: SDKM/1.5.0.7774 (ubuntu1604)
13:19:44.062 - warn: Registering a callback with no name for event: Session sta$
13:19:44.352 - warn: Registering a callback with no name for event: Session sta$
13:19:44.352 - warn: Registering a callback with no name for event: Report comp$
13:19:44.352 - warn: Registering a callback with no name for event: Report comp$
13:19:44.354 - info: downloadMetrics.reset
13:19:44.355 - warn: Registering a callback with no name for event: Session sta$
13:19:44.355 - warn: Registering a callback with no name for event: Session res$
13:19:44.356 - warn: Registering a callback with no name for event: Session sta$
13:19:44.357 - warn: Registering a callback with no name for event: Session end$
13:19:44.357 - warn: Registering a callback with no name for event: File init d$
13:19:44.357 - warn: Registering a callback with no name for event: File pendin$
13:19:44.357 - warn: Registering a callback with no name for event: File starte$
13:19:44.357 - warn: Registering a callback with no name for event: File finish$
13:19:44.357 - warn: Registering a callback with no name for event: File checks$
13:19:44.358 - warn: Registering a callback with no name for event: Component i$
13:19:44.358 - warn: Registering a callback with no name for event: Component s$
13:19:44.358 - warn: Registering a callback with no name for event: Component f$
13:19:44.358 - warn: Registering a callback with no name for event: Component f$
13:19:44.358 - warn: Registering a callback with no name for event: Component f$
13:19:44.359 - warn: Registering a callback with no name for event: Session sta$
13:19:44.359 - warn: Registering a callback with no name for event: Component f$
13:19:44.369 - warn: Registering a callback with no name for event: Active bund$
13:19:44.369 - warn: Registering a callback with no name for event: Component f$
13:19:44.372 - info: Forking worker process
13:19:44.385 - info: Initializing the download service
13:19:44.390 - info: Download service pid is: 2257
13:19:44.391 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:19:44.392 - warn: Registering a callback with no name for event: File downlo$
13:19:44.392 - warn: Registering a callback with no name for event: File finish$
13:19:44.392 - warn: Registering a callback with no name for event: Session sta$
13:19:44.392 - warn: Registering a callback with no name for event: File downlo$
13:19:44.392 - warn: Registering a callback with no name for event: File finish$
13:19:44.392 - warn: Registering a callback with no name for event: File reset $
13:19:44.392 - warn: Registering a callback with no name for event: File downlo$
13:19:44.392 - warn: Registering a callback with no name for event: Component i$
13:19:44.393 - warn: Registering a callback with no name for event: Component s$
13:19:44.393 - warn: Registering a callback with no name for event: Component p$
13:19:44.393 - warn: Registering a callback with no name for event: Component f$
13:19:44.393 - info: Download manager can use up to 16 download threads per file
13:19:44.393 - warn: Registering a callback with no name for event: Session sta$
13:19:44.437 - info: create .sdkm.bashrc under /home/(hide)/.nvsdkm/.sdkm.bashrc
13:19:44.451 - info: installMetrics.reset
13:19:44.451 - warn: Registering a callback with no name for event: Session sta$
13:19:44.452 - info: uninstallMetrics.reset
13:19:44.452 - warn: Registering a callback with no name for event: Active bund$
13:19:44.453 - warn: Registering a callback with no name for event: Active bund$
13:19:44.453 - warn: Registering a callback with no name for event: Component f$
13:19:44.453 - warn: Registering a callback with no name for event: File finish$
13:19:44.453 - warn: Registering a callback with no name for event: Component f$
13:19:44.453 - warn: Registering a callback with no name for event: Session sta$
13:19:44.453 - warn: Registering a callback with no name for event: Session res$
13:19:44.453 - warn: Registering a callback with no name for event: Session pau$
13:19:44.453 - warn: Registering a callback with no name for event: Session com$
13:19:45.560 - warn: Registering a callback with no name for event: File starte$
13:19:45.560 - warn: Registering a callback with no name for event: File downlo$
13:19:45.560 - warn: Registering a callback with no name for event: File checks$
13:19:45.560 - warn: Registering a callback with no name for event: File finish$
13:19:45.750 - warn: Registering a callback with no name for event: Active bund$
13:19:45.753 - warn: Registering a callback with no name for event: Terminal ou$
13:19:45.753 - warn: Registering a callback with no name for event: Login progr$
13:19:45.753 - warn: Registering a callback with no name for event: undefined
13:19:45.754 - warn: Registering a callback with no name for event: Component d$
13:19:45.754 - warn: Registering a callback with no name for event: Component p$
13:19:45.754 - warn: Registering a callback with no name for event: Component s$
13:19:45.754 - warn: Registering a callback with no name for event: File starte$
13:19:45.754 - warn: Registering a callback with no name for event: Component i$
13:19:45.754 - warn: Registering a callback with no name for event: Component f$
13:19:45.754 - warn: Registering a callback with no name for event: Component f$
13:19:45.754 - warn: Registering a callback with no name for event: Component f$
13:19:45.754 - warn: Registering a callback with no name for event: Group finis$
13:19:45.754 - warn: Registering a callback with no name for event: Component f$
13:19:45.754 - warn: Registering a callback with no name for event: Session pau$
13:19:45.754 - warn: Registering a callback with no name for event: Session res$
13:19:45.757 - info: Logger level is set to: info
13:19:46.022 - warn: Registering a callback with no name for event: Login progr$
13:19:46.022 - warn: Registering a callback with no name for event: CLI Abort
13:19:46.100 - info: Front-end main function (startMain) was called
13:19:46.191 - info: Creating auto update task
13:19:46.211 - info: Host OS: ubuntu1604
13:19:46.212 - info: packageJson: /opt/nvidia/sdkmanager/resources/app/package.$
13:19:46.227 - info: [Download Service]:Download service is initializing
Download service was initialized
Got heartbeat request

13:19:46.227 - info: [Download Service] Download service is alive
13:19:46.672 - info: Application configuration is:
{
mainRepoURL: 'https://developer.download.nvidia.com/sdkmanager/sdkm-config/ma$
PIDServer: ‘P’,
DevZoneServer: ‘P’,
StarfleetServer: ‘P’
}
13:19:46.756 - info: manifest: {“name”:“sdkmanager”,“releaseVersion”:“1.5.0”,"r$
13:19:46.756 - info: Telemetry parameters are: title: SDK Manager 1.5.0.7774 ve$
13:19:46.757 - info: autoLogin failed: Aborting auto login since there is no lo$
13:19:46.757 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:19:46.757 - info: Telemetry: allow = . isGDPRAllowed=false
13:19:46.763 - info: mainRepoUrl: https://developer.download.nvidia.com/sdkmana$
13:19:46.764 - info: logging in with l1 url: https://developer.download.nvidia.$
13:19:46.891 - info: Create timing task for auto update successfully.
13:19:51.686 - info: logging in to starfleet server
13:19:51.687 - info: Logging in with starfleet login method…
13:19:51.691 - info: Event: Login Progress: undefined
13:19:52.807 - info: Listening to Starfleet Redirect URL on port: 8080
13:19:52.807 - info: Listening to Starfleet Development signin URL on port: 368$
13:19:52.808 - info: Openning login URL in browser: https://login.nvidia.com/a$
13:19:52.810 - info: Event: Login Progress: Waiting for user to complete login $
13:20:59.015 - info: Got Starfleet server signin response. Request URL: /?ui_l$
13:20:59.016 - info: Event: Login Progress: Authenticating with NVIDIA server…
13:20:59.017 - info: Event: Login Progress: Login credentials retrieved success$
13:20:59.023 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:20:59.023 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:00.531 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:00.537 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:02.618 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:02.635 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:02.635 - error: Failed to get user information from Starfleet. Error: Req$
13:21:02.635 - info: Event: Login Complete: failed
13:21:02.635 - error: loginManager.login failed: Failed to get client token
13:21:02.641 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:10.859 - info: logging in to starfleet server
13:21:10.860 - info: Logging in with starfleet login method…
13:21:10.872 - info: Event: Login Progress: undefined
13:21:10.881 - info: Listening to Starfleet Development signin URL on port: 448$
13:21:10.881 - info: Openning login URL in browser: https://login.nvidia.com/a$
13:21:10.885 - info: Event: Login Progress: Waiting for user to complete login $
13:21:42.699 - info: Got Starfleet server signin response. Request URL: /?ui_l$
13:21:42.699 - info: Event: Login Progress: Authenticating with NVIDIA server…
13:21:42.700 - info: Event: Login Progress: Login credentials retrieved success$
13:21:42.702 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:42.702 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:43.728 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:43.783 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:45.840 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:45.857 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$
13:21:45.858 - error: Failed to get user information from Starfleet. Error: Req$
13:21:45.877 - info: Event: Login Complete: failed
13:21:45.877 - error: loginManager.login failed: Failed to get client token
13:21:50.839 - warn: [Proxy Agent] invalid proxy settings - {“proxyMode”:"manua$

17

Dear @hiroki.omatsu.df,
Did you set proxy in sdkmanager as given in SDK Manager Settings :: NVIDIA SDK Manager Documentation ?

18

Yes, I did
I made the settings on both System Configuration and Manual Configuration
I also checked my ID and password

19

Dear @hiroki.omatsu.df,
Thanks for clarification. Could you attach the ~/.nvsdkm/sdkm.log as a file.
You can also use the Settting->Export Debug Log and attach the file here.

20

This is log file

SDKM_logs_2021-06-09_11-32-34.zip (19.9 KB)

Thanks

21

The problem has been solved
What I tried was to make sure that the proxy settings on my host PC and the proxy settings on the SDK manager were correct.
Thank you so much

1 Like