I ran some standard updates on the Ubuntu machine I have hosting my discourse instance. Now I cannot start discourse again. I’m not a docker user, but the instructions I inherited from a previous staff member who set this up are to run: ./launcher stop app ./launcher rebuild data ./launcher rebuil…

Wow. In that case please do upload the output to something like pastebin or gist, and share the link here.

OK, I’ve pasted here: https://gist.github.com/anonymous/6464801c6cde865ab60e3f10dba21e05

Thanks. Here is something concerning Bundler::HTTPError: Net::HTTPTooManyRequests: <html> <head><title>429 Too Many Requests</title></head> <body bgcolor="white"> <center><h1>429 Too Many Requests</h1></center> <hr><center>nginx</center> </body> </html> You are hitting the rate limit for rubygems…

Thanks for spotting that. I have no idea what I can do about that though - I’m just running the commands that are meant to work with Discourse. I can’t even find any results for rubygem rate limits. Every time we have had to do anything that involved restarting this server, Discourse breaks and I h…

I’m afraid there’s nothing you can do about that short of waiting a bit before re-issuing your rebuild command or contacting rubygems.

[Bild] shaneoh: Do you mean that the rebuild could work if I try it later on? Pretty sure it will unless your IP has been blacklisted. The only way to know for certain is to contact rubygems.org . [Bild] shaneoh: It seems to me that the problem is that the rebuild job itself involves too …

[Bild] zogstrip: Pretty sure it will unless your IP has been blacklisted. The only way to know for certain is to contact rubygems.org . When I’ve contacted them I’ve gotten no response. [Bild] zogstrip: From what I’ve seen, it only happens when using a VPS (where you don’t know what the o…

You have a multicontainer setup and is starting app before data. Try the other way around.

Would you mind telling me the exact series of commands you would recommend running? I’ve just tried this and get the same issue: ./launcher stop data ./launcher stop app ./launcher start data ./launcher start app ./launcher rebuild app

Unable to start discourse due to rubygems rate limiting

Unterstützung

shaneoh 18. Juli 2017 um 13:53 11

Do you mean that the rebuild could work if I try it later on? It seems to me that the problem is that the rebuild job itself involves too many requests and is therefore impossible. I can see others have stumbled across this recently too.

Thema		Antworten	Aufrufe
Update failing due to rate limiting by RubyGems Support	40	5795	18. Dezember 2020
Rubygems: Too Many Requests problem returns! Support	18	3502	17. März 2022
The only solution I have found to workaround «429 Too Many Requests» failure from rubygems.org Support	5	2575	27. Oktober 2017
Failing to rebuild app on Discourse since May 7 Self-hosting	14	2165	13. Juni 2019
Problem when updating Discourse Forum Self-hosting unsupported-install	20	2124	29. Juni 2023

Unable to start discourse due to rubygems rate limiting

Verwandte Themen