Help! My Discourse instance is offline

Installation
1

After an upgrade of docker I get ‘bad gateway’.

I tried:

  • re-install docker and rebuild it
  • checked IP addresses
  • checked if server is only
  • server can be connected through Putty
  • activated Docker Doctor

Please suggest me how to get it back online :slight_smile:

2 Likes
2

YOu likely just needed to wait another minute or two for the server to finish starting up.

4 Likes
3

You’re right – thanks for pointing me in the right direction.

2 Likes
4

So you’re back up and it’s working again?

3 Likes
5

Unfortunately not,

It looks like the Discourse instance is 75% reachable after the rebuild… but after that, it turns 502 bad gateway again.

When the setup is finished (rebuild) - it’s offline again.

3 Likes
6

It’s expected to be down during the rebuild.

It takes a minute or two after a rebuild for everything to get started up.

Do you have enough disk space?

3 Likes
7

Thanks for your comment.

Yes, I am familiar with the period after the rebuild. But we are 10 minutes further and the website is still offline.

Yes, we have 160GB of disk space.

image
image1000×308 31.1 KB

1 Like
8

Then you likely have some other problem, perhaps a plugin. YOu can look at

  tail -f /var/discourse/shared/standalone/log/rails/production.log

Or something very much like that

1 Like
9

Completed 200 OK in 43ms (Views: 0.2ms | ActiveRecord: 0.0ms | Allocations: 1349 9)
Started POST “/t/6242/notifications.json” for 172.71.102.181 at 2023-03-08 14:43 :49 +0000
Processing by TopicsController#set_notifications as JSON
Parameters: {“notification_level”=>3, “topic_id”=>“6242”, “topic”=>{}}
Can’t verify CSRF token authenticity.
Completed 200 OK in 10ms (Views: 0.1ms | ActiveRecord: 0.0ms | Allocations: 2675 )
Deprecation notice: SiteSetting.enable_personal_messages has been deprecated. Please use SiteSetting.personal_message_enabled_groups instead. (removal in Di scourse 3.0)
At /var/www/discourse/lib/site_setting_extension.rb:199:in public_send
Rendered layouts/email_template.html.erb (Duration: 2.2ms | Allocations: 775)

Parameters: {“external_id”=>“19929.json”}
Completed 200 OK in 43ms (Views: 0.2ms | ActiveRecord: 0.0ms | Allocations: 1349 9)
Started POST “/t/6242/notifications.json” for 172.71.102.181 at 2023-03-08 14:43 :49 +0000
Processing by TopicsController#set_notifications as JSON
Parameters: {“notification_level”=>3, “topic_id”=>“6242”, “topic”=>{}}
Can’t verify CSRF token authenticity.
Completed 200 OK in 10ms (Views: 0.1ms | ActiveRecord: 0.0ms | Allocations: 2675 )
Deprecation notice: SiteSetting.enable_personal_messages has been deprecated. Please use SiteSetting.personal_message_enabled_groups instead. (removal in Di scourse 3.0)
At /var/www/discourse/lib/site_setting_extension.rb:199:in public_send
Rendered layouts/email_template.html.erb (Duration: 2.2ms | Allocations: 775)

Thanks for helping me out @pfaffman.

Unfortunately, I am not able to fix it.

Can I hire you to fix this issue, please?

2 Likes
10

@pfaffman helped me out! Thanks!

It was a typo in our app.yml

4 Likes
11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.