Tell me, what could be the error? After the restart, the discourse stopped running. Logs can be seen by reference https://pastebin.com/DzUPNhAT

Remove the discourse-rss-poster plugin and try again.

[image] Falco: Remove the discourse-rss-poster plugin and try again. He’s getting throttled by Rubygems. Where are you hosted?

[image] Falco: discourse-rss-poster Thanks huge for the help, after removal of a plug-in discourse-rss-poster, discourse has successfully restarted. @LeoMcA what can be problematic with your plugin? You can view?

[image] 11145: Thanks huge for the help, after removal of a plug-in discourse-rss-poster, discourse has successfully restarted. @LeoMcA what can be problematic with your plugin? You can view? If you read the errors, you’re being throttled by rubygems. So your issue wasn’t that plugin per se, but that you got throttled.

Well, you can wait 24 hours and try re-enabling the plugin and doing another rebuild, maybe by then rubygems might not be throttling you (though to be honest, I’m not sure I see it as a throttling issue, considering the error happens between two rubygem downloads/installs… that or I’m reading the output wrong).

[image] 11145: Tell me, how can I fix this? The issue is that your ip block is likely hammering the rubygems server…the solution is likely to use something like DigitalOcean, I rarely have this issue. Something is weird but this is not a discourse issue, you should contact rubygems – you can read more about it here. I never actually saw this issue. I use Rackspace for the discourse instance I maintain…I’d bet money this is an AWS issue.

Tried to plugin the plugin discourse-rss-poster , but the same error https://pastebin.com/H8dSU9CF

[image] 11145: Tried to plugin the plugin discourse-rss-poster , but the same error https://pastebin.com/H8dSU9CF You are being throttled due to hitting the rate limit by rubygems. I repeat: this is not a discourse issue. Look at line 639 onwards in your paste and read it ;).

One other thing you could do: install another plugin in place of discourse-rss-poster – does that cause you to hit the rate limit as well? I suspect it will.

Are you using a plain Ubuntu AMI, or did you take a prebuilt one from the marketplace? Last week someone was having similar problems with an Intuz pre-built AMI - the issues went away when they moved to a plain Ubuntu 16 AMI and migrated their instance. See here: https://meta.discourse.org/t/upgrade-error-on-aws-free-tier-t2-micro/63756

Error after restarting the discourse

Product Support

11145 (Алексей Копаев) June 11, 2017, 5:49am 17

Answered in a personal

Topic		Replies	Views
Update failing due to rate limiting by RubyGems Product Support	39	6232	June 12, 2018
The only solution I have found to workaround «429 Too Many Requests» failure from rubygems.org Product Support	4	2639	October 27, 2017
Unable to start discourse due to rubygems rate limiting Product Support	43	3901	June 14, 2018
Error when rebuilding/upgrading discourse due to bad plugin Self-hosting	1	1065	December 26, 2017
Can we start discourse after failed rebuild? Product Support	3	1110	June 10, 2018

Error after restarting the discourse

Related topics