It just so happens that we haven’t updated Discourse in a very long time. We’re currently at v2.8.5. I recently discovered that Discourse is well beyond version 3. I’d like to update to the current version, but for now, I’d like to at least update to the latest version 2.8.x - 2.8.14. And here’s a…

─# docker version Client: Docker Engine - Community Version: 28.1.1 API version: 1.49 Go version: go1.23.8 Git commit: 4eba377 Built: Fri Apr 18 09:52:18 2025 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community…

I removed all plugins from app.yaml. This didn’t help: FAILED -------------------- Pups::ExecError: grep -q 'outlets/before-server' /etc/nginx/conf.d/discourse.conf || ( >&2 echo 'The "before-server" Nginx outlet is missing. This version of discourse_docker is not compatible with the chosen Discour…

Please share your app.yml file, sans passwords.

[이미지] nahimov: Pups::ExecError: grep -q 'outlets/before-server' /etc/nginx/conf.d/discourse.conf || ( >&2 echo 'The "before-server" Nginx outlet is missing. This version of discourse_docker is not compatible with the chosen Discourse version.' ; exit 1 ) failed with return #<Process::Status: pid…

This is full log: └─# ./launcher rebuild app x86_64 arch detected. WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.yml Ensuring launcher is up to date Fetching origin Launcher is up-to-date Stopping old container + /usr/bin/docker …

[이미지] nahimov: This version of discourse_docker is not compatible with the chosen Discourse version.' It’s a good bet that your OS it out of date too. The easiest and safest thing to do is move to a new vm with an up-to-date OS and docker.

[이미지] Falco: Please share your app.yml file, sans passwords. Here’s the original app.yml. I obfuscated it a bit. It has all the plugins. For testing, I removed them all, but rebuilding still produces an error. app.yml (4.9 KB)

[이미지] pfaffman: It’s a good bet that your OS it out of date too. The easiest and safest thing to do is move to a new vm with an up-to-date OS and docker. Ubuntu 20.04 is still fine, and has all the latest packages. Docker Engine 28.1.1 is also quite up-to-date. And why migrate to another VM…

[이미지] nahimov: Ubuntu 20.04 is still fine, and has all the latest packages. https://ubuntu.com/blog/ubuntu-20-04-lts-end-of-life-standard-support-is-coming-to-an-end-heres-how-to-prepare [이미지] nahimov: Docker Engine 28.1.1 is also quite up-to-date. See my above quote from the logs. …

[이미지] pfaffman: Because the postgres upgrade can be problematic and installing on a new VM assures that you can’t end up with a broken forum. PostgreSQL is installed separately in Docker, and updating it is no problem. [이미지] pfaffman: That’s not going to work because the current docker c…

구버전 2.8.5 업그레이드 문제

지원 자체 호스팅

pfaffman (Jay Pfaffman) 11월 20, 2025, 2:59오후 8

운영체제도 오래되었을 가능성이 큽니다. 가장 쉽고 안전한 방법은 최신 운영체제와 Docker가 설치된 새로운 가상 머신으로 이전하는 것입니다.

글		댓글	조회수
Upgrade failed spectacularily Support	25	978	2월 10, 2025
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2267	11월 26, 2021
Forum not working after update – what’s missing? Self-hosting	35	795	9월 4, 2025
An upgrade knocked my site offline; how long until it's restored? Self-hosting	15	538	7월 10, 2025
Update Not Completed and Discourse not opening Self-hosting	16	694	6월 17, 2024

구버전 2.8.5 업그레이드 문제

Related topics