Error 500 after command line rebuild

I am running Discourse in Docker using the official docker container

After issuing
./launcher rebuild app

I am presented with

Oops

The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience.

Detailed information about the error was logged, and an automatic notification generated. We’ll take a look at it.

No further action is necessary. However, if the error condition persists, you can provide additional detail, including steps to reproduce the error, by posting a discussion topic in the site’s feedback category.

Can anyone help me with this? I am getting this (see image below) warning, however I do not think it is the cause. I do not have any plug-ins enabled. i.e the git clone repos for them are commented out in the app.yml file.

Try a git pull before rebuild

cd /var/discourse
git pull
./launcher rebuild app
1 Like

I have done a git pull however I am greeted with this issue.

1 Like

is there anyway to recover the database and create a new instance of this?

You need to provide the full build logs, your screenshot is a tiny fraction. Paste it into pastebin or similar and link it.

1 Like

There isn’t any issue afaik. These look to me like fairly normal console logs that pop up around rebuild.

Agreed that the deprecation logs are normal, but it is returning an error 500.

Which plugins are you using?

The plugins that are enabled are listed below:
docker_manager
babble
discourse-chat-integration

At the moment the page simply does not load anything. it appears blank. /logs does load but no links work. /safe-mode loads but will not load after hitting the “Enter Safe Mode” button.

Here is a pastebin of the output build.
./launcher rebuild app > ~/discourse_build.log

https://pastebin.com/7Za2D7NJ

Also can you try ./launcher enter app
then do curl http://localhost:3000 and see what the output is

The output from curl http:/localhost:3000
https://pastebin.com/wYaA3N5c

Thanks, that didn’t help like I thought it would, sorry about that!

ok try this:
I looked at your site headers with curl,

Content-Security-Policy: base-uri 'none'; object-src 'none'; 
script-src 'report-sample' http://mechassaultonline.com/logs/ 
http://mechassaultonline.com/sidekiq/ 
http://mechassaultonline.com/mini-profiler-resources/ 
http://mechassaultonline.com/assets/ 

etc etc. so first change your site name in containers/app.yml to www.mechassaultonline.com and rebuild, then check the force https checkbox at https://www.mechassaultonline.com/admin/site_settings/category/all_results?filter=https. That should do it!

combination of that. and this ->

Looks like everything is up and running. thanks for all the help!