[iShot_2023-06-25_17.18.20] Hello everyone! I was trying to update the discourse forum using the link posted in admin panel and i got this error. The whole forum just gone. What should i do now to reset the update? Thanks a lot if anyone could help me. :sob:

In fact it means that your forum is being updated. - unless you interrupt the update before it finishes. Try visiting your forum https://yoursite.com/latest.json. If it returns something, then wait 10 minutes and see if the problem resolves itself

Thanks for your reply, I tried the method you gave and it returns 502 Bad Gateway nginx.

It looks like you may have to ./launcher rebuild app

I tried the ./launcher rebuild app and i got following error messages: FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle install --deployment --retry 3 --jobs 4 --verbose --without test development' failed with return # Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --retry 3 --jobs 4 --verbose --without test development'"]} 6e9e60bd6b6113cdcb001127fd2a24fe86f2a1658bf24500e5e2b720fd793510 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. ./discourse-doctor may help diagnose the problem. and i scrolled up and found some possible errors logs: 1)200:M 25 Jun 2023 16:00:16.252 # Failed listening on port 6379 (TCP), aborting. 2)[DEPRECATED] The `--deployment` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local deployment 'true'`, and stop using this flag [DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local without 'test development'`, and stop using this flag 3)Bundler::PathError: The path `/var/www/discourse/vendor/bundle/ruby/2.7.0/bundler/gems/sprockets-f4d3dae71ef2` does not exist. 4)Bundler::InstallError: sass-embedded-1.63.6-x86_64-linux requires rubygems version >= 3.3.22, which is incompatible with the current version, 3.2.18

Someone else encountered a similar issue recently if this is any help? [image] Long pause in standard installation of command : cd /var/www/discourse && su discourse -c 'bundle install --retry 3 --jobs 4' Self-hosting hello guys! i am a new user of discourse from china ,and i meet a strange issue in standard installation after execute the command ./discourse-setup, my terminal stuttered on command for a long time ( more than 20 minutes) I, [2023-06-04T07:47:29.161469 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle config --local deployment true' I, [2023-06-04T07:47:29.544117 #1] INFO -- : I, [2023-06-04T07:47:29.544260 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle co…

Thanks a lot for your reply, but i guess it is not the same problem, my server is at Germany. I’m using discourse docker image for my server. What should i do if ./launcher rebuild app doesn’t work?

Looks similar to Rebuild failed due to ruby gem incompatibility

Thanks for your help! Yes, it looks similar and I tried: my server:/var/discourse**$ git pull fatal: Not a git repository: ../.git/modules/discourse_docker Should i do something before running git pull? I was doing this in my server’s /var/discourse.

Seems possible you have an unusual setup - is this a standard install?

I read the last programmer’s documents for me and it says because many things of the web running behind nginx and discourse also needs to be hosted behind nginx. The standard install doesn’t work for my situation. and the following is how he said in the document and how he did: Discourse runs in a docker container. However, it requires a special kind of configuration, not via a docker-compose.yml or a .conf file. The discourse-project/ the github repository required to config and build the docker-image can be found here. Ignore the nice and juicy “discourse-setup” program they provide, that won’t work here. We need to configure the app ourselves. clone discourse_docker to /var/discourse: git clone https://github.com/discourse/discourse_docker.git /var/discourse go to the folder and use a provided sample configuration: cd /var/discourse && cp samples/standalone.yml containers/app.yml then edit the containers/app.yml file (e.g. with sudo nano) Changes were made to the hosting section, the smtp settings for mail and - important - the expose section so only an unused port is exposed to the outside To run discourse on a path such as “/forum” some more changes were needed as described here Some problems also occur with the email-authentication: The mail that sends emails is here “server’s email”. However, Discourse expects the mail to have the same domain as its host, namely “server’s email” Solution described here Also use “DISCOURSE_SMTP_AUTHENTICATION: login” as another env option. Why also always . . . Then build the app from the /var/discourse directory with sudo ./launcher bootstrap app. This takes quite a while Then you may be able to start the discourse container with sudo ./launcher start app.

Problem when updating Discourse Forum

Product Support Self-hosting

whitewaterdeu (mocha3901) June 26, 2023, 1:30am 16

hello jammy, after times of fail installation , i found it’s caused by memory limit of server and network, i suggest you to use a server of 4GB Mem and access normally of github and ruby

Topic		Replies	Views
Discourse update error Self-hosting	35	2715	January 30, 2023
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2484	November 26, 2021
Discourse offline after failed upgrade "bootstrap failed with exit code 5" Self-hosting	24	1754	February 22, 2024
Forum not working after update – what’s missing? Self-hosting	35	1052	September 4, 2025
Update Not Completed and Discourse not opening Self-hosting	16	854	June 17, 2024

Problem when updating Discourse Forum

Related topics