Getting 502 Bad Gateway after attempting upgrade

CocoQuark · December 30, 2024, 6:25pm

You’re hitting a rate limit from Docker.

Many users were able to resolve the issue by disabling IPv6.

Error response from daemon: toomanyrequests: Too Many Requests (HAP429)

opened 09:46PM - 20 Nov 24 UTC

Hi, Thank you for providing the support to every single case when this appears.… In my case it happened all of the sudden, without any changes on sysadmin so I have no idea how to determine if I have a loose script running wild with the requests, would you please be so kind to provide some stats, or possible causes? Project is hosted on VPS with IP 51.75.74.139. I can't docker push anything, not even login or pull: ``` docker login -u **** Password: Error response from daemon: login attempt to https://registry-1.docker.io/v2/ failed with status: 429 Too Many Requests ``` ``` docker pull nginx Using default tag: latest Error response from daemon: toomanyrequests: Too Many Requests (HAP429). ``` Thank you!

Similar issue:

Topic		Replies	Views
502 Bad Gateway after online rebuild of tests-passed Production just now Installation	5	395	January 13, 2024
Discourse suddenly not accessible anymore Installation	6	782	June 5, 2024
Error connecting to Redis on localhost:6379 Installation	2	2623	June 10, 2019
Help! Upgrade constantly fails Installation	7	627	April 3, 2023
Forum dead after docker_manager upgrade Installation	3	557	January 4, 2020

Getting 502 Bad Gateway after attempting upgrade

Related topics