[image] I am seeing this update message in my admin panel, but it doesn’t give me the option to update from the site, and mentions I need to use “./launcher rebuild app” to update. I have done that, but it still stays on 3.6.0 beta3. This is in my container/app.yml for the branch. ##Which Git revision should this container use? (default: latest) #version: latest I have also tried a “./launcher destroy app” and then another rebuild, but it seems that 3.6.0 beta3 is the current image. Any insight as to what’s going on here? As far as I can tell, I am running the latest image and discourse version, but it still nags me about a critical update.

ℹ️ Discourse v3.6.0.beta3-latest — https://github.com/discourse/discourse/commits/9bb15488bd — Ember v6.6.0 BUT…. turns out I’m just an idiot.. disregard this thread. I moved my forum from a dedicated VM to my normal webserver some time ago, and forgot that I did that. I’ve updated it on the webserver and it has updated just fine (after a cloudflare cache reset). I guess I should shut down this VM so I don’t forget again in the future. Really sorry for wasting everyone’s time, and thanks for your help! [image]

Why is it needed? Doesn’t a rebuild do a get pull?

Around this time there was a lot of interesting changes around the shift to the new release naming: [תמונה] RFC: A new versioning strategy for Discourse Development Those three tags have now been moved to the correct commit manually. Will make sure that the automated tooling is updated to keep them in the right place going forward. * commit 48167b94d63faf8a41b9c8193ec5dd3e4e9f498e (HEAD -> release/2025.11, tag: release, tag: latest-release, tag: beta, origin/release/2025.11) | Author: Joffrey JAFFEUX | Date: Wed Nov 26 14:31:55 2025 +0100 | | Backport limited body overflow (#36256) | I think this build might have fallen foul of this, so git pull is worth a try.

[תמונה] raskulous: mentions I need to use “./launcher rebuild app” to update. I have done that, but it still stays on 3.6.0 beta3 Are you 100% sure that the rebuild succeeded? No error messages? I can’t think of any reason you’d be left on 3.6.0.beta3 after a successful rebuild :thinking:

The only reason why I didn’t think this might be the issue, is they were apparently still “online” … (which wouldn’t be the case after a failed rebuild)

Yeah that’s true. Although there are situations where launcher rebuild can fail before it shuts down the existing container (e.g. not enough disk space on the machine) The other thing I’d recommend is opening the browser console and checking what the :information_source: line says. It should have a version number, and a link to the precise commit hash.

[תמונה] david: e.g. not enough disk space on the machine) yes, and on that note @raskulous if git pull doesn’t do it, try a ./launcher cleanup app before a rebuild too, for good measure!

root@halflife /var/discourse (main) $ git pull Already up to date. root@halflife /var/discourse (main) $ ./launcher cleanup app WARNING! This will remove all stopped containers. Are you sure you want to continue? [y/N] y Deleted Containers: a58277545d443da8b94056b18921a1f1a075ba0e74cdae77796694c58a5d6906 Total reclaimed space: 0B WARNING! This will remove all images without at least one container associated to them. Are you sure you want to continue? [y/N] y Deleted Images: deleted: sha256:6ddbd1a96a1946ec6bb77c75bd76f6f90d4c4a8b724caeb0b6c66e09ddafd38d deleted: sha256:adf730c0bcf566afc3c3d67d942d11f68644bfa2413d43878bf180dc5c697d23 deleted: sha256:818c4d787c1b1d6c9764a55ebd48660366aa4bf885b422a74b114ebdd27df5b7 deleted: sha256:59fed181a2fe6072d783d00cb165845de654160410e187e58fa7c227f08ba69a untagged: discourse/base:2.0.20251003-1437 untagged: discourse/base@sha256:0db7c9b4598e2a1806658391669d791fd779aa4301fdfbed6a7f322bf64e66ab deleted: sha256:e1f8b0b3fb45852cee16025371f9b0be02a1a1aecc300fde77394b40fb5a736d deleted: sha256:d3efe4e5e3c3d2402e7a037be02ebf5ae755fc810b3598e51e343b84e763716f deleted: sha256:cd092d63ff1918ba841ef29a3b58c68cea176d44080e7df9b7f347f00bd93b1a deleted: sha256:5cbdf0ed25a8fe97bfbc24185d02c58844a57450a3f86fc7d5a558fd232ab4ab deleted: sha256:403aa6c20a051b2d5c745dc7a435af9df41757d993a993e6631f899aa0bb486e deleted: sha256:3afcd50bd91ec84e258277e9e23da6cac2427c0375a78df88946b79d30b1d44b deleted: sha256:7489ca900cbd55786d357445f33a65b0b11e3261db274d58ccabe77bd4e0fe9d deleted: sha256:71c52c9ead7800839744288a4af6d83d500532ea7f9855d524c6afa074c63a60 deleted: sha256:0b33a182fac1d26fef0bb788c3e866051abd1b3cd63086388f0fe8ff7c45941c deleted: sha256:e5ccd79dd23e97a74c15ef20b17e01a70377f5832a260af90b6693f4508cbfa3 deleted: sha256:93abe37c16bdf7fef8141b1377f0ce0104afd44abb77b10f5ed79d9db83f5e9e deleted: sha256:b904c7d18289155e7f30b6bf3c70f70b83cf7a30a64994953aaf208794757948 deleted: sha256:21071147a1da14eb4df3db0d8cab94e814fa732c13bb61e759300e5ac18abee7 deleted: sha256:990a81a661827e957f92dd3f2696b736dcb2a98abc25e5782768eeffbf5c7192 deleted: sha256:4cbf227e956f5b11ceeb5b55847d08727d947d2517219806a475586c84333ec3 deleted: sha256:2a2ac8595545fcf1c83ddb9fa2942e41aad400ab130dcd11a930b8b78a51f1b5 deleted: sha256:25297b21ea784d4feab472ca411628f2b828e54d491bfad343ba0ef7bdc445ca deleted: sha256:0f8c3c379f72c1933ca5de2d8234d1d2e68ceb96a4f115e68bb219d6bf21529c deleted: sha256:d3442f9b520eb026ed03bf55cc93bded85c44c219f195a7635b74153dce18ffa deleted: sha256:f05243ffd6e01ff377d6565691221ef1cd11d37c7bedc8e2eaad478ae8668e1f deleted: sha256:d4e8473543b3ac427ed2d3c0e6bd02e1bd67ae99487d88280ec6a93431c30d5f deleted: sha256:99be84708bfcb1db25137b395dd37a1a7997ab8fc68bc3b0264fa1a59fbd824f deleted: sha256:d1c4ec063756f9d4823e44c0531ec77a3a4f8867b1b6649243163ed0f2fd3ed5 deleted: sha256:29f68a6145ecb2ebf1ff0bc119cf56cd78af2e8736c3a10e78d96d75cc5e228f deleted: sha256:57dc1b3ee11f2615b880d2f110c4780f41884e95a8ee5475fd4218a1f879b637 deleted: sha256:4e34d8cc8d9622192e7a4cb8fc70cba85837041ecf6bdf4e8d2ccb820aae70f5 deleted: sha256:54240fc4d72a665dd583c27d7af430dea2074964edfb1bc992e31c8e94dfa15a deleted: sha256:9b2aac547dae88002b7826bea7dff202234919cce4295363035af4f1ad894c02 deleted: sha256:5d7d1eb160a4d66dfb5eb978a07dd9aa79f22c19450fa7486755062d799174d8 deleted: sha256:eb5f13bce9936c760b9fa73aeb1b608787daa36106cc888104132e353ed37252 untagged: discourse/base:2.0.20260209-1300 untagged: discourse/base@sha256:50d2dae489a9c9916c3d50d880f7f1282fcbe179339b60a8947ab135c1f1f9bf deleted: sha256:024087fcba8d55efdce231c261ff2e8ab2d6c9df15a60e4f183d0dd8fc7d1758 deleted: sha256:cc071f07ff387f4836bbd81b14853ee4ec3778b2bfe7b4b46a920b1eb20f275a deleted: sha256:01acad9c96eca87cdc72a29ce5181f21c23bdf7084de96fe441cc2e1f54d8c4e deleted: sha256:15cff7c3d6efabf7261738c696fcb1b0b041e67113c883260cd632f5990f37a1 Total reclaimed space: 5.973GB Seems to have found a bunch of stale images which is great. It still has not updated after a rebuild, though. No errors in the output of the rebuild that I can see. Is there a log that you’d like me to attach for more information? Here’s what I have in my rails logs: root@halflife /var/discourse (main) $ ./launcher enter app x86_64 arch detected. WARNING: This output is designed for human readability. For machine-readable output, please use --format. root@halflife-app:/var/www/discourse# cd /shared/log/rails root@halflife-app:/shared/log/rails# ls -al total 240 drwxr-xr-x 2 discourse www-data 4096 Feb 19 07:38 . drwxr-xr-x 4 root root 4096 Nov 12 05:23 .. -rw-r–r-- 1 discourse www-data 0 Feb 19 07:38 production_errors.log -rw-r–r-- 1 discourse www-data 20 Feb 13 07:40 production_errors.log-20260213.gz -rw-r–r-- 1 discourse www-data 20 Feb 14 07:54 production_errors.log-20260214.gz -rw-r–r-- 1 discourse www-data 20 Feb 15 07:46 production_errors.log-20260215.gz -rw-r–r-- 1 discourse www-data 20 Feb 16 07:46 production_errors.log-20260216.gz -rw-r–r-- 1 discourse www-data 20 Feb 17 07:45 production_errors.log-20260217.gz -rw-r–r-- 1 discourse www-data 20 Feb 18 07:50 production_errors.log-20260218.gz -rw-r–r-- 1 discourse www-data 0 Feb 19 07:38 production_errors.log-20260219 -rw-r–r-- 1 discourse www-data 77488 Feb 19 22:05 production.log -rw-r–r-- 1 discourse www-data 20 Feb 13 07:40 production.log-20260213.gz -rw-r–r-- 1 discourse www-data 20 Feb 14 07:54 production.log-20260214.gz -rw-r–r-- 1 discourse www-data 20 Feb 15 07:46 production.log-20260215.gz -rw-r–r-- 1 discourse www-data 20 Feb 16 07:46 production.log-20260216.gz -rw-r–r-- 1 discourse www-data 20 Feb 17 07:45 production.log-20260217.gz -rw-r–r-- 1 discourse www-data 20 Feb 18 07:50 production.log-20260218.gz -rw-r–r-- 1 discourse www-data 0 Feb 19 07:38 production.log-20260219 -rw-r–r-- 1 discourse www-data 0 Feb 19 07:38 sidekiq.log -rw-r–r-- 1 discourse www-data 20 Feb 13 07:40 sidekiq.log-20260213.gz -rw-r–r-- 1 discourse www-data 20 Feb 14 07:54 sidekiq.log-20260214.gz -rw-r–r-- 1 discourse www-data 20 Feb 15 07:46 sidekiq.log-20260215.gz -rw-r–r-- 1 discourse www-data 20 Feb 16 07:46 sidekiq.log-20260216.gz -rw-r–r-- 1 discourse www-data 20 Feb 17 07:45 sidekiq.log-20260217.gz -rw-r–r-- 1 discourse www-data 20 Feb 18 07:50 sidekiq.log-20260218.gz -rw-r–r-- 1 discourse www-data 0 Feb 19 07:38 sidekiq.log-20260219 -rw-r–r-- 1 discourse www-data 12701 Feb 19 18:02 unicorn.stderr.log -rw-r–r-- 1 discourse www-data 20 Feb 13 07:40 unicorn.stderr.log-20260213.gz -rw-r–r-- 1 discourse www-data 20 Feb 14 07:54 unicorn.stderr.log-20260214.gz -rw-r–r-- 1 discourse www-data 20 Feb 15 07:46 unicorn.stderr.log-20260215.gz -rw-r–r-- 1 discourse www-data 20 Feb 16 07:46 unicorn.stderr.log-20260216.gz -rw-r–r-- 1 discourse www-data 20 Feb 17 07:45 unicorn.stderr.log-20260217.gz -rw-r–r-- 1 discourse www-data 20 Feb 18 07:50 unicorn.stderr.log-20260218.gz -rw-r–r-- 1 discourse www-data 0 Feb 19 07:38 unicorn.stderr.log-20260219 -rw-r–r-- 1 discourse www-data 1543 Feb 19 18:02 unicorn.stdout.log -rw-r–r-- 1 discourse www-data 20 Feb 13 07:40 unicorn.stdout.log-20260213.gz -rw-r–r-- 1 discourse www-data 20 Feb 14 07:54 unicorn.stdout.log-20260214.gz -rw-r–r-- 1 discourse www-data 14032 Feb 15 07:46 unicorn.stdout.log-20260215.gz -rw-r–r-- 1 discourse www-data 20 Feb 16 07:46 unicorn.stdout.log-20260216.gz -rw-r–r-- 1 discourse www-data 20 Feb 17 07:45 unicorn.stdout.log-20260217.gz -rw-r–r-- 1 discourse www-data 20 Feb 18 07:50 unicorn.stdout.log-20260218.gz -rw-r–r-- 1 discourse www-data 0 Feb 19 07:38 unicorn.stdout.log-20260219

the rebuild log you see on the console when you ./launcher rebuild app - this is not a log file. … which is long, but ideally you want to look right at the end to see if it raised an error and look further back to find the actual error (if there was one)

Yeah, I don’t see any errors at the end of the launcher rebuild, and it starts up fine. The last few lines remove the old container and start up the new one, no errors there.

Beta update to 2026.1

תמיכה התקנה

merefield (Robert) 19 בפברואר,‏ 2026,‏ 9:09pm 2

on this occasion, perform a git pull before the rebuild

נושא		תגובות	צפיות
Trouble upgrading from 3.3.0.beta1 to 3.3.0.beta6 Self-hosting	22	677	8 באוגוסט,‏ 2024
./launcher rebuild app command not found Self-hosting	6	2798	10 בספטמבר,‏ 2019
./launcher rebuild app for old 1.6 discourse not working Self-hosting	12	1006	25 בינואר,‏ 2023
Upgrade link no longer works Self-hosting	7	1189	22 בנובמבר,‏ 2021
Error upgrading Self-hosting	12	1805	20 באוקטובר,‏ 2016

Beta update to 2026.1

נושאים קשורים