|
| 1 | +--- |
| 2 | +description: Learn how to troubleshoot common Docker Hub issues. |
| 3 | +keywords: hub, troubleshoot |
| 4 | +title: Troubleshoot Docker Hub |
| 5 | +linkTitle: Troubleshoot |
| 6 | +weight: 60 |
| 7 | +tags: [Troubleshooting] |
| 8 | +toc_max: 2 |
| 9 | +--- |
| 10 | + |
| 11 | +If you experience issues with Docker Hub, refer to the following solutions. |
| 12 | + |
| 13 | +## You have reached your pull rate limit (429 response code) |
| 14 | + |
| 15 | +### Error message |
| 16 | + |
| 17 | +When this issue occurs, you receive following error message in the Docker CLI or |
| 18 | +in the Docker Engine logs: |
| 19 | + |
| 20 | +```text |
| 21 | +You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limits |
| 22 | +``` |
| 23 | + |
| 24 | +### Possible causes |
| 25 | + |
| 26 | +- You have reached your pull rate limit as an authenticated Docker Personal |
| 27 | + user. |
| 28 | +- You have reached your pull rate limit as an unauthenticated user based on your |
| 29 | + IPv4 address or IPv6 /64 subnet. |
| 30 | + |
| 31 | +### Solution |
| 32 | + |
| 33 | +You can use one of the following solutions: |
| 34 | + |
| 35 | +- [Authenticate](./usage/pulls.md#authentication) or |
| 36 | + [upgrade](../subscription/change.md#upgrade-your-subscription) your Docker |
| 37 | + account. |
| 38 | +- [View your pull rate limit](./usage/pulls.md#view-hourly-pull-rate-and-limit), |
| 39 | + wait until your pull rate limit decreases, and then try again. |
| 40 | + |
| 41 | +## Too many requests (429 response code) |
| 42 | + |
| 43 | +### Error message |
| 44 | + |
| 45 | +When this issue occurs, you receive following error message in the Docker CLI or |
| 46 | +in the Docker Engine logs: |
| 47 | + |
| 48 | +```text |
| 49 | +Too Many Requests |
| 50 | +``` |
| 51 | + |
| 52 | +### Possible causes |
| 53 | + |
| 54 | +- You have reached the [Abuse rate limit](./usage/_index.md#abuse-rate-limit). |
| 55 | + |
| 56 | +### Solution |
| 57 | + |
| 58 | +1. Check for broken CI/CD pipelines accessing Docker Hub and fix them. |
| 59 | +2. Implement a retry with back-off solution in your automated scripts to ensure |
| 60 | + that you're not resending thousands of requests per minute. |
| 61 | + |
| 62 | +## 500 response code |
| 63 | + |
| 64 | +### Error message |
| 65 | + |
| 66 | +When this issue occurs, the following error message is common in the Docker CLI |
| 67 | +or in the Docker Engine logs: |
| 68 | + |
| 69 | +```text |
| 70 | +Unexpected status code 500 |
| 71 | +``` |
| 72 | + |
| 73 | +### Possible causes |
| 74 | + |
| 75 | +- There is a temporary Docker Hub service issue. |
| 76 | + |
| 77 | +### Solution |
| 78 | + |
| 79 | +1. View the [Docker System Status Page](https://www.dockerstatus.com/) and |
| 80 | + verify that all services are operational. |
| 81 | +2. Try accessing Docker Hub again. It may be a temporary issue. |
| 82 | +3. [Contact Docker Support](https://www.docker.com/support/) to report the issue. |
0 commit comments