Hello, I am using Ubuntu. After the classic server update I had to restart the server. After restarting, Discourse started giving error 502 then 503. My resources are sufficient, if they were not sufficient, it would never have worked before. When I run the ./launcher rebuild app command, I get th…

The problem was solved as follows. I changed the version: value in app.yml to version: stable and rebuilt.

What version of docker do you have? docker --version Can you start the old container with ./launcher start app

Docker version 24.0.7, build 24.0.7-0ubuntu2~20.04.1 ./launcher start app output: Nothing to do, your container has already started!

[afbeelding] Mehmet: Pups::ExecError: cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean' failed with return #<Process::Status: pid 301 exit 1> Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn' ex…

Thank you for your message, but since I have been looking for a solution since the morning, I visited the page you mentioned. The instruction on this page did not solve my problem. I made the necessary configuration on app.yml. I think I made a wrong or incomplete explanation. I have no problems wit…

I was assuming you are on the “tests-passed” version of Discourse, but based on the yarn related errors, it seems you are on the “stable” version. What branch and version of Discourse is your site on?

It should be in the latest version. Where can I learn?

[afbeelding] Finding what version of Discourse you're using Using Discourse bookmark This guide explains how to find the version of Discourse you’re using by inspecting the website’s source code. person_raising_hand Required user level: All users Understandi…

I can’t see this part because my Discourse is stuck on the 502 or 503 error page. Such a meta tag does not occur in the item review section.

YOU can also look for tests-passed or discourse_version in your yml file to see what version you have there.

I added the code you specified into App.yml. The result is as follows. app 2.0.20240708-0023: Pulling from discourse/base Digest: sha256:025e9c1f6848c4726544c6ae873d710c62f547b72afb7f537aaa44eb5377cb5c Status: Image is up to date for discourse/base:2.0.20240708-0023 docker.io/discourse/base:2.0.202…

Ik kan Discourse niet starten

Ondersteuning Installatie

Moin 23 september 2024 om 15:54 8

Topic		Antwoorden	Weergaven
Discourse Installation Failure on Fresh Server: FAILED TO BOOTSTRAP Self-hosting	11	1093	7 mei 2023
Unable to boostrap Discourse since last upgrade Self-hosting	4	763	22 januari 2023
Discourse stopped working all of a sudden Self-hosting	8	401	6 juli 2024
Discourse update error Self-hosting	35	2305	30 januari 2023
Continuous Issues when Rebuilding Discourse Self-hosting	5	719	19 maart 2024

Ik kan Discourse niet starten

Gerelateerde topics