Hello We have simply clicked the admin upgrade button. Did not expect this: Oops The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience. Detailed information about the error was logged, and an automatic notification generated. We'll take…

Are you still able to access /logs on your forum? That is where the notification went. The last two questions can only be answered after you have looked at it.

Nothing worked anymore unfortunately. So we had to re-instantiate a backup server side, and now we are a bit wary of updating again. Is there any way to update in safe mode ? I can hardly believe that every time the software updates we would have to run a risk of total downtime.

[이미지] Beda: that every time the software updates we would have to run a risk of total downtime That is a real risk with every app, including Discourse. That’s why big guys are using a stage server and we smaller fishes are doing backups (site AND database) before every update, but at least be…

Hello and welcome @smileBeda :slightly_smiling_face: Could you give us some more detail about your set up? For instance, what version you’re running, whether it’s a standard install , and if you have any plugins (official or third-party). Normally upgrades go very smoothly, though taking a backup o…

We are running 2.9.0.beta8 The update it asks us to do is docker_manager 45986ad4 ( Comparing 45986ad40ec642ea617a083aecc75e0078878fb7...90a8a6c6cae0bba01de7fdf340da1ab878bff913 · discourse/docker_manager · GitHub ) It is a standard install from docker, however we run a couple plugins (but nothing u…

[이미지] Beda: It is a standard install from docker, however we run a couple plugins (but nothing unusual, really. No custom code so far) Can you paste your app.yml file here? It will make it easier to see what was and what is.

There are also some good pointers on how to manually update from the server in this topic: [이미지] Manually update Discourse and Docker image to latest Self-Hosting bookmark This guide provides step-by-step instructions for manually updating Discourse, the Docke…

Did you do a ./launcher rebuild app Or did you upgrade from the web interface? The full rebuild is sometimes required. The logs you’re looking for are in /var/discourse/shared/log/rails/production.log (if I typed it right on my phone)

[이미지] Jay Pfaffman: /var/discourse/shared/log/rails/production.log (if I typed it right on my phone) close enough :grin: /var/discourse/shared/standalone/log/rails/production.log and maybe /var/discourse/shared/standalone/log/rails/production_errors.log

[이미지] Beda: however we run a couple plugins Could you please elaborate on this? Which plugins?

2.9.0.beta8에서 업그레이드 후 사이트가 손상되어 복구 불가

제품 지원 자체 호스팅

JammyDodger 8월 31, 2022, 11:08오전 9

이 주제에서는 서버에서 수동으로 업데이트하는 방법에 대한 좋은 팁도 찾을 수 있습니다:

./launcher rebuild app 명령은 종종 좋은 대안(Plan B)이 될 수 있으며, 이 과정에서 오류가 발생하면 위로 스크롤하여 내용을 읽어볼 수 있습니다.

글		댓글	조회수
Site down after UI update Self-hosting	7	525	5월 18, 2024
An upgrade knocked my site offline; how long until it's restored? Self-hosting	15	676	7월 10, 2025
Update Discourse Error Self-hosting	4	342	5월 14, 2024
Update error, website unavailable, possibly plugin related? Self-hosting	2	1453	1월 12, 2018
Upgraded but admin page says out of date Product Support	21	3019	5월 12, 2015

2.9.0.beta8에서 업그레이드 후 사이트가 손상되어 복구 불가

Related topics