Before you start

Authentication tokens, image manifests and layers are separate stages; HTTP 429 often indicates a rate limit.

Step by step

  1. Use https://docs.docker.com/docker-hub/ to confirm supported platforms and official clients.
  2. Record the OS and app version and preserve existing settings before changing DNS, VPN or proxies.
  3. Compare Wi-Fi and cellular settings; desktop clients may also have terminal or app-specific proxies.
  4. Pull one small public image and record whether authentication, the manifest or a layer download fails.
  5. Test a minimal sample and review background operation, notifications and file permissions as needed.
  6. Re-enable extensions, routing rules and synchronization one at a time after basic functionality works.

Official references

Use these provider resources for current rules. Some announcement links are help pages, not live availability tests.

Common questions

Can switching networks fix every Docker Hub error?

No. Account privileges, subscriptions, file permissions and service outages require separate checks.

What should I send to support?

Share the time, client version, redacted error code and minimal reproduction. Never share a password, token, cookie or one-time code.