Hi all, I think I broke my site by clicking on Upgrade on “Discourse-Manager” if I recall correctly. It declared failure and I clicked on a box “reset upgrade” or sth. Cannot reproduce the actions precisely, as the site is down. What I found out so far is that Rails does not connect to Redis, and I cannot rebuild app. Not sure how to proceed with this.. Rails production log says: Error connecting to Redis on localhost:6379 (Errno::EADDRNOTAVAIL) subscribe failed, reconnecting in 1 second. Call stack /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/redis-4.8.1/lib/redis/client.rb:398:in rescue in establish_connection’` ./launcher rebuild app: Error response from daemon: toomanyrequests: Too Many Requests (HAP429). Error response from daemon: toomanyrequests: Too Many Requests (HAP429). Unable to find image 'discourse/base:2.0.20241203-0251' locally docker: Error response from daemon: toomanyrequests: Too Many Requests (HAP429). See 'docker run --help'. Your Docker installation is not working correctly

You’re hitting a rate limit from Docker. Many users were able to resolve the issue by disabling IPv6. https://github.com/docker/hub-feedback/issues/2421 Similar issue: [image] Docker Rate Limit Error on Launcher Rebuild Support Turning off IPv6 on the Digital Ocean server solved the issue: Here is instruction from DO on how to turn off IPv6.

Getting 502 Bad Gateway after attempting upgrade

Product Support Self-hosting

dudenas December 30, 2024, 9:57pm 3

Thank you, disabling ipv6 worked!

Topic		Replies	Views
Discourse Update Error: Your Docker installation is not working correctly Product Support	7	401	February 8, 2025
Docker Rate Limit Error on Launcher Rebuild Product Support	12	1012	December 24, 2024
429 Too Many Requests on /admin/upgrade page Self-hosting	11	5129	April 28, 2017
Site down: 502 Bad Gateway - after update Self-hosting	2	1246	September 24, 2018
Redis Error after upgrade Self-hosting	13	1898	June 3, 2020

Getting 502 Bad Gateway after attempting upgrade

Related topics