Docker Community Forums

Share and learn in the Docker community.

Too many failed login attempts


(Develvts) #1

After change from Tutum to DockerCloud, i have login problems:

docker login -e Email -u Username -p PASSWORD
Error response from daemon: Login: Too many failed login attempts. You have been locked out for one hour. Try again later or contact support.

We use jenkins pipeline for deploy to preproduction and production, and we login every time we redeploy.


(Develvts) #2

Waiting 24h, fixed.

This is a 24h ban ?


(Commercetools) #3

We are using travis and are also seeing this error:

docker login
Username (xyz):
Error response from daemon: Login: Too many failed login attempts. You have been locked out for one hour. Try again later or contact support. (Code: 429; Headers: map[Content-Type:[application/json] Vary:[Cookie] X-Frame-Options:[SAMEORIGIN] Strict-Transport-Security:[max-age=31536000] Server:[nginx/1.6.2] Date:[Fri, 08 Apr 2016 08:47:30 GMT]])

The credentials are correct since it works again after some time.


(Commercetools) #4

Any ideas why this happens?


(Levin Keller) #5

What a bad implementation. I am locked out. This is a very good DOS-attack on our deployment. Stop this docker!


(Beckend) #6

Same here, was trying to push image for about an hour… Only after 100+ attempts it finally started to push…

Improving a network would be nice…

Seems like their network is overloaded or some limits are configured…


(Tmds) #7

What is the proper way to unlock the account once you are in the “too many failed login attempts for username or IP address” state?


(Mshand) #8

It should reset after 10 minutes.


(Robert Buck) #9

I forgot to update my credentials, and … Is this for real? I pay for a service that bans me for attempting to update from K8S? OMG!


(Venketesan) #10

I have been locked out of hub.docker.com for 48 hours now. I never put in a wrong password and it just happened all of a sudden with the daemon failing to push. I have sent multiple emails to support@docker.com This is quite ridiculous for a production grade service


(Davig) #11

Not sure if this will help anyone but I had this problem and it turned out I was logged in two browser sessions at the same time. Logged out of the browsers and was able to login at the command line.