Ottenere un errore 502 Bad Gateway dopo aver tentato l'aggiornamento

Canapin · 30 Dicembre 2024, 6:25pm

Stai raggiungendo un limite di frequenza da Docker.

Molti utenti sono stati in grado di risolvere il problema disabilitando IPv6.

github.com/docker/hub-feedback

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

opened 09:46PM - 20 Nov 24 UTC

closed 02:05PM - 09 Apr 25 UTC

asntcrz

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. 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!

Problema simile:

Argomento		Risposte	Visualizzazioni
Discourse Update Error: Your Docker installation is not working correctly Support	7	166	Febbraio 8, 2025
Docker Rate Limit Error on Launcher Rebuild Support	13	574	Dicembre 24, 2024
429 Too Many Requests on /admin/upgrade page Installation	12	4919	Aprile 28, 2017
Site down: 502 Bad Gateway - after update Installation	3	1171	Ottobre 24, 2018
Redis Error after upgrade Installation	14	1593	Luglio 3, 2020

Ottenere un errore 502 Bad Gateway dopo aver tentato l'aggiornamento

Argomenti correlati