Hi, Today, after updating my self-hosted Discourse from 3.4.0.beta3-dev to 3.4.0.beta3 via command line, the site is not accessible. It shows Bad Gateway (nginx) page. May I know what’s gone wrong? P/s Currently, I have restored my server back to 3.4.0.beta3-dev condition again. Thanks for any p…

Note this does not look like a segfault to me: LoadError: /var/www/discourse/vendor/bundle/ruby/3.3.0/extensions/aarch64-linux/3.3.0/mini_racer-0.17.0.pre12/mini_racer_extension.so: undefined symbol: __libc_single_threaded (LoadError) Likely this is caused cause the actual running container is so…

The Bad Gateway page will be there for a while, as this happens on my forum as well. Give about 5-10 minutes, it should be alright. If you see a 504 Timeout error, you can wait a while more and periodically reload te page. At least, that’s what I do. Your forum should be up after that.

Unfortunately I had waited for more than 30 min, still the same.

If I update via console, no error. But if I update via UI, there was an error, something like the update process failed, and the Reset Update button was not shown.

I tried to update again via UI, and below is the error log: Start Updating ******************************************************** *** Please be patient, next steps might take a while *** ******************************************************** Cycling Unicorn, to free up memory Restarting unicorn…

The error screen: [Screenshot 2025-02-01 at 10.51.52 AM]

After the error, the site cannot be visited: [Screenshot 2025-02-01 at 10.52.07 AM]

Try a rebuild from the command-line.

I tried already, using: cd /var/discourse ./launcher rebuild app The result is Bad Gateway

Also, from the error log, it seems the error is weird: Docker Manager: FAILED TO UPGRADE via the UI, you MUST upgrade Docker first before you are allowed to upgrade Discourse, don’t know why it still showed Docker Manager upgrade failure. [Screenshot 2025-02-01 at 11.01.54 AM]

Error Updating from 3.4.0.beta3-dev to 3.4.0.beta3

Product Support Self-hosting

NateDhaliwal (Nate Dhaliwal) January 31, 2025, 6:00am 4

Hmm… were there any errors in the console when you were switching to 3.4.0beta3?

Topic		Replies	Views
Upgrade error for v3.2.0.beta3 Product Support two-container	1	554	November 13, 2023
2.6.0 beta 3 update failed on disk and/or memory space Self-hosting server-resources	28	3020	September 26, 2020
Production install on 3.4.0.beta2-dev failing to update to 3.4.0.beta2 Self-hosting	11	584	November 2, 2024
"Waiting for unicorn to reload", then update stops Product Support	30	5119	June 20, 2021
Failed upgrade from 2.9.0.beta14 to 3.1.0.beta Self-hosting	10	1337	January 25, 2023

Error Updating from 3.4.0.beta3-dev to 3.4.0.beta3

Related topics