### Author:  [@Adam\_Price](https://meta.discourse.org/u/Adam_Price)
#### Post date: [November 1, 2024, 9:29pm UTC](https://meta.discourse.org/t/discourse-broken-after-failed-upgrade/334095/1 "2024-11-01T21:29:04Z")
I did a bad thing. I inherited a discourse server for my organization. For months now, every time I log in, it has told me there are critical updates that must be installed (3.2.x → 3.3.x). I finally caved, and clicked on the updates in the admin panel. The docker update was fine - that finished fairly quickly, and everything was still working afterwards. Then I clicked on the 3.3 discourse update. It proceeded for a while, then threw up this error message:
```plaintext
Bundle complete! 146 Gemfile dependencies, 185 gems now installed.
Gems in the groups 'development' and 'test' were not installed.
Bundled gems are installed into `./vendor/bundle`
Post-install message from i18n:
PSA: I18n will be dropping support for Ruby < 3.2 in the next major release (April 2025), due to Ruby's end of life for 3.1 and below (https://endoflife.date/ruby). Please upgrade to Ruby 3.2 or newer by April 2025 to continue using future versions of this gem.
1 installed gem you directly depend on is looking for funding.
Run `bundle fund` for details
$ yarn install
yarn install v1.22.19
info No lockfile found.
[1/5] Validating package.json...
error discourse@: The engine "yarn" is incompatible with this module. Expected version "please-use-pnpm". Got "1.22.19"
warning discourse@: The engine "pnpm" appears to be invalid.
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Docker Manager: FAILED TO UPGRADE
#
```
I had time to copy this, but when I hit the back button, it was apparent that the server is completely down.
```plaintext
" 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."
```
While I appreciate the reassurance here that it is being taken care of, I am fairly sure that I am the one who is supposed to be taking care of it.
Suggestions on where to start?
---
### Author:  [@omarfilip](https://meta.discourse.org/u/omarfilip)
#### Post date: [November 1, 2024, 9:40pm UTC](https://meta.discourse.org/t/discourse-broken-after-failed-upgrade/334095/2 "2024-11-01T21:40:33Z")
Have you tried upgrading from the command line?
> [@Manually update Discourse and Docker image to latest](https://meta.discourse.org/t/manually-update-discourse-and-docker-image-to-latest/23325):
>
> 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…
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [November 1, 2024, 9:40pm UTC](https://meta.discourse.org/t/discourse-broken-after-failed-upgrade/334095/3 "2024-11-01T21:40:33Z")
Can you please try a rebuild on the command line?
---
### Author:  [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [November 2, 2024, 12:28am UTC](https://meta.discourse.org/t/discourse-broken-after-failed-upgrade/334095/4 "2024-11-02T00:28:13Z")
As suggested. Every now and then you will want to perform a command line update. Especially when the web interface fails. Most of the time a command line updates will resolve an update issue from the dashboard
---
### Author:  [@Adam\_Price](https://meta.discourse.org/u/Adam_Price)
#### Post date: [November 2, 2024, 12:31am UTC](https://meta.discourse.org/t/discourse-broken-after-failed-upgrade/334095/5 "2024-11-02T00:31:58Z")
Thanks everyone - a command line update and an increase in the virtual disk size did the trick.
We’re back online, with 3.4.
Phew.