I did a rebuild tonight, and it failed, I disabled all plugins, and it is still failing, unfortunately. It appears some of the gems may not be updating properly. @pfaffman I may need your assistance on this. FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bund…

If requests to rubygems are timing out then that’s likely a problem at their end. Have you successfully restarted the existing container? I’m assuming other DNS requests from the server are succeeding?

No, I have not been able to start the container Here’s my output from gem env fyi RubyGems Environment: - RUBYGEMS VERSION: 2.5.2.1 - RUBY VERSION: 2.3.1 (2016-04-26 patchlevel 112) [x86_64-linux-gnu] - INSTALLATION DIRECTORY: /var/lib/gems/2.3.0 - USER INSTALLATION DIRECTORY: /root/.gem/r…

EDIT: Wrong. Well, this was bizarre. It turns out that if you dont’ follow the instructions in Discourse FontAwesome Pro and clone the plugin with the others instead of in a after_code stanza, you get these errors. I can’t explain why it worked before. I looked back through the instructions there to…

[image] Jay Pfaffman: if you dont’ follow the instructions in Discourse FontAwesome Pro and clone the plugin with the others instead of in a after_code stanza, you get these errors I don’t understand what you’re saying Jay, the normal way of installing a plugin is to clone it in an after_cod…

Now I’m really confused. I never noticed which block the plugins are normally in. But I swear it didn’t work with the plugin with all of the others and then I added another after_code block with the git clone and the install script. I’ll see if I can break it again. :confused: :crying_cat_face:

Well, best I can tell, it was just rubygems rate limiting. I’m not quite sure how the brand new droplet I spun up was rate limited, but that, or a spurious issue with rubygems itself, is my best explanation.

Try adding 127.0.0.1 to host dns. That worked for me for this error.

Reconstruction échouée, aidez-moi s'il vous plaît !

Soutien Installation

Chandra Septembre 28, 2022, 4:08 8

Essayez d’ajouter 127.0.0.1 à votre DNS hôte.
Cela a fonctionné pour moi pour cette erreur.

Sujet		Réponses	Vues
Installation Failed: Plugins Self-hosting	7	2286	Août 12, 2017
Update failing due to rate limiting by RubyGems Support	39	6127	Juin 12, 2018
Update Fails with Unexpected Error During Rebuild Self-hosting	9	1413	Décembre 16, 2023
Urgent, rebuild failed from old version Self-hosting	5	547	Mai 8, 2023
Rebuild failed - FAILED TO BOOTSTRAP Self-hosting	20	2304	Décembre 28, 2023

Reconstruction échouée, aidez-moi s'il vous plaît !

Sujets connexes