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 a look at it. No further action is necessary. However, if the error condition persists, you can provide additional detail, including steps to reproduce the error, by posting a discussion topic in the site’s feedback category.

i think you had this issue before? [图片] Oops The software powering this discussion forum encountered an unexpected problem Support 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 a look at it. No further action is necessary. However, if the error condition persists, you can provide additional detail, including steps to reproduce the error, by posting a discussion topic in the site’s feedback category. [图片] Manually update Discourse and Docker image to latest Self-Hosting bookmark This guide provides step-by-step instructions for manually updating Discourse, the Docker container, and the Ubuntu operating system on a self-hosted setup. person_raising_hand Required user level: System Administrator warning SSH access to the server. If you self-host Discourse, you occasionally need to run a manual update via the command line to get the latest security releases and newest libraries. These updates are not picked up in admin/upgrade, which is why you’ll occa…

I’m afraid that’s a very generic message and we’ll need more details to help you out. Are there any more details in your /logs or in the browser console? Does it work in safe mode?

You can also try a Command Line rebuild - which is explained here: Manually update Discourse and Docker image to latest

@nwnuyhs, checking in, did you end up figuring out what the issue was?

The reason may be that the browser was closed during the update process. Finally, use ./launcher rebuild app to solve the problem.

[图片] Yang Hongsheng: the browser was closed during the update process This is not correct. You can close the browser during the update process and it will still continue. It is possible that the update was not yet finished. Sometimes you have to wait a few minutes and then after a hard refresh the site will come back. But yes if you can the command line update is always going to work more smoothly, though your site will be offline during the entire update process which can take a little while depending on what all is being updated.

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 a look at it. No further action is necessary. However, if the error condition persists, you can provide additional detail, including steps to reproduce the error, by posting a discussion topic in the site’s feedback category. https://baidu.do/

Hello,MS.Lily， Happy new year, thanks for your reminder, I rebuild,now the website is ok

Thank you :slight_smile: Happy new year to you too! I am glad you have your site back up and running.

哎呀，驱动本讨论区的软件遇到一个意外问题

产品支持

HamMan2118 2024 年9 月 3 日 11:16 3

您也可以尝试命令行重建 - 此处有详细说明：Manually update Discourse and Docker image to latest

话题		回复	浏览量
Site down after UI update Self-hosting	7	546	2024 年5 月 18 日
Update Not Completing Product Support	1	163	2025 年3 月 27 日
Crash After Recent Update Product Support	2	185	2024 年9 月 3 日
Empty update page？ Product Support	2	710	2022 年6 月 14 日
Update Discourse Error Self-hosting	4	350	2024 年5 月 14 日

哎呀，驱动本讨论区的软件遇到一个意外问题

相关话题