# 公告：通过GUI升级3.3.3到3.4.0失败，只能通过命令行重建

**URL:** <https://meta.discourse.org/t/psa-stable-3-3-3-3-4-0-upgrade-via-gui-failed-had-to-rebuild-via-command-line/351100>\
**Category:** Self-hosting\
**Created:** [2025年二月7日 16:04 UTC](https://meta.discourse.org/t/psa-stable-3-3-3-3-4-0-upgrade-via-gui-failed-had-to-rebuild-via-command-line/351100 "2025-02-07T16:04:16Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![rahim123](https://avatars.discourse-cdn.com/v4/letter/r/df705f/32.png) [@rahim123](https://meta.discourse.org/u/rahim123)\
**Post date:** [2025年二月7日 16:04 UTC](https://meta.discourse.org/t/psa-stable-3-3-3-3-4-0-upgrade-via-gui-failed-had-to-rebuild-via-command-line/351100/1 "2025-02-07T16:04:16Z")

</div>

Just a heads-up for self-hosted `stable` branch users. For me the upgrade via the GUI failed, I’m not sure if this would happen to everyone, as I saw some errors about unicorn processes, which tends to be a random issue in my experience. But at any rate that left my forum in a state where it claimed to be up-to-date in `/admin/update` while still being stuck on the old version.

So I had to SSH into the server and `/var/discourse/launcher rebuild app` _two times_, the first time it just upgrades Postgres:

```plaintext
UPGRADE OF POSTGRES COMPLETE

Old 13 database is stored at /shared/postgres_data_old

To complete the upgrade, rebuild again using:

./launcher rebuild app

```

And the second time it finishes the rest of the upgrades.

After that was all over and verifying that my data was intact I also did a `/var/discourse/launcher cleanup` to get rid of the huge backup file that it created for the old database.

---

_[View the full topic](https://meta.discourse.org/t/psa-stable-3-3-3-3-4-0-upgrade-via-gui-failed-had-to-rebuild-via-command-line/351100)._