Reputation: 5620

Docker desktop sign in failed, but sign in from web was successful

Tried to Sign in from Docker desktop, got the following error:

Post "https://login.docker.com/oauth/token":
dialing login.docker.com:443 with direct connection:
connecting to 104.16.83.103:443:
dial tcp 104.16.83.103:443:
connectex:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

mobile hotspot is used.

Upvotes: 0

Answers (8)

Steven T

Reputation: 41

A solution for this problem for me was downgrading to an older version. I used the oldest I could get from https://docs.docker.com/desktop/release-notes/ I went to Docker Desktop 4.24.2 and login works as expected. I can confirm I had login trouble in versions 4.37.2 and 4.38.0. I work on Windows 11 Enterprise.

I had tried signing in using CLI, config.json and some other proposed solutions. Logging in using CLI succeeds in terminal, but that does NOT log me in into the Docker Desktop App.

Upvotes: 0

LagSeeing

Reputation: 73

Use socket5 for https proxy, it will work.

like this

Upvotes: 0

ARUN Raghav

Reputation: 1

We need to create a key to sign in with docker desktop. Try to follow these steps: https://docs.docker.com/desktop/get-started/

After that, click on the sign-in button on docker desktop.

Docs tell me to run this code.

gpg --generate-key pass init <your_generated_gpg-id_public_key> docker pull molly/privateimage The third code threw a permission error in my case, but then also the sign-in button worked after the first two steps.

If it doesn't work, try this: https://docs.docker.com/security/for-admins/configure-sign-in/

Upvotes: 0

TossACoin

Reputation: 21

Similar conditions for me. If you are using proxy, get its http and https address, then in docker desktop, go to settings-resources-proxy, enable manual and fill in the first two lines with the address above. Work for me.

Upvotes: 1

Jayasimha Reddy

Reputation: 1

In case of successful login, you can also login through CLI by below command:

docker login -u username -p password

Upvotes: 0

aakash4dev

Reputation: 1176

We need to make a key to sign in with the docker desktop. Try to follow these steps: https://docs.docker.com/desktop/get-started/

After that click on sign-in button on the docker desktop.

Docs tell me to run this code.

gpg --generate-key
pass init <your_generated_gpg-id_public_key>
docker pull molly/privateimage

The third code gave a permission error in my case, but then also sign-in button worked after the first two steps.

If it don't worked. Try this: https://docs.docker.com/security/for-admins/configure-sign-in/

Upvotes: 0

user23332457

Reputation: 1

You can try restarting your docker desktop in the troubleshoot section and restarting your pc or else you can change your wifi connection and you can try again.

Upvotes: 0

carloswm85

Reputation: 2416

I had a similar problem:

Post "https://login.docker.com/oauth/token": writing response to 
login.docker.com:443: connecting to 10.1.33.254:80: dial tcp 10.1.33.254:80: 
connectex: A connection attempt failed because the connected party did not 
properly respond after a period of time, or established connection failed 
because connected host has failed to respond.

Also, log in was successful using browser, but it failed when trying to login using the desktop Docker up.

In my case, the solution was to disable the Proxy configurations I had set in my device.

Just delete or disable all the data used by the app to go through the proxy, and maybe your log in will be successful.

Also, consider that your mobile spot connection may be conflicting with some connection setting at app level. Do you have the same issue while trying to connect using other connections?

Upvotes: 1

Docker desktop sign in failed, but sign in from web was successful

Answers (8)

Related Questions