Too many login attempts about dockercloud-haproxy

[tifayuki]

@svenmueller
There is a PR(https://github.com/docker/dockercloud-haproxy/tree/prevent_retrying_on_401) that does not retry the API request when receiving a 401 error. This can mitigate the chance of locking your account, when the API key becomes invalid. The changes will also apply to all our system containers. Hope this can be helpful.

[tifayuki]

@svenmueller

That means you have too many login attempts with wrong credentials. It could be caused by you leave some containers running on a node has been removed from the dockercloud.

Please open a ticket to the support and ask them to unlock you account.

[svenmueller]

@tifayuki as you can see in the logs the this is triggered by haproxy container itself when running in Docker cloud (using stackfile). The question is why this happens.

[svenmueller]

Same problem is reported here: #29

[tifayuki]

@svenmueller
As I said, when API call returns 429, it means your account is blocked for a security reason. This is usually because of too many requests(logins, api calls, etc.) with an invalid credentials. To know the exact reason that causes the account lock, you need to the docker support team.

[tifayuki]

This is related to API throttling, and we are keep optimizing it on the server side.
Not really an error of this haproxy image, and I am going to close this issue at the moment.
If you still have such a problem, please contact support@docker

[svenmueller]

@tifayuki contacting the Docker support resulted in no answer. And yes we still see this issue. I would like to re-open this issue.

[evanp]

@tifayuki that sounds great. I've only seen this problem on BYON nodes on Docker Cloud, by the way.