Error 500 after command line rebuild

Product Support Self-hosting

AI-generated summary

User jdelmore encountered a 500 error after running ./launcher rebuild app in a Docker-based Discourse installation. Initial troubleshooting included checking for plugins (none enabled), performing a git pull itsbhanusharma, and reviewing logs. Despite normal-looking deprecation logs itsbhanusharma, the site remained unresponsive, with blank pages and broken links, though /logs and /safe-mode loaded partially. jdelmore shared build logs via Pastebin, and alextheblade suggested testing via curl http://localhost:3000, which revealed CSP header issues. The solution involved updating the site name in app.yml to www.mechassaultonline.com, rebuilding, and enabling “force HTTPS” in site settings alextheblade. jdelmore confirmed the fix worked, citing a helpful meta.discourse.org thread on CSP policy errors after rebuild. The root cause was misconfigured CSP headers due to an incomplete or incorrect site URL setup.

1

I am running Discourse in Docker using the official docker container
https://github.com/discourse/discourse_docker

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.

2

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.

image
image720×158 7.82 KB

3

Try a git pull before rebuild

cd /var/discourse
git pull
./launcher rebuild app
4

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

image
image718×407 13.3 KB

5

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

6

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

7

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

8

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

9

Which plugins are you using?

10

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

11

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

12

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

13

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

15

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!

16

combination of that. and this →

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