# Upgrading from /admin/upgrade takes \*very\* long

**URL:** <https://meta.discourse.org/t/upgrading-from-admin-upgrade-takes-very-long/256879>\
**Category:** Bug\
**Created:** [March 2, 2023, 8:33pm UTC](https://meta.discourse.org/t/upgrading-from-admin-upgrade-takes-very-long/256879 "2023-03-02T20:33:01Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [March 6, 2023, 9:04pm UTC](https://meta.discourse.org/t/upgrading-from-admin-upgrade-takes-very-long/256879/13 "2023-03-06T21:04:02Z")

</div>

Note… for fix to take effect, there is a bit of a chicken meets egg situation. Old code is still loaded when you run the upgrade.

You may need a `./launcher rebuild` for the first time, and subsequent times the web upgrader will be fine.

No easy way around this. @cvx its a tricky problem… technically we should have it so `DockerManager::Upgrader.new(user_id, repo, repo_version).upgrade` shells out and runs new upgrader code when it upgrades … but its a can of snakes.

### Fast workaround

1. Start upgrading docker manager
2. Cancel when it gets stuck
3. `./launcher restart app` from the shell
4. Upgrade from web will work.

### Easy workaround

1. `./launcher rebuild app`

Everything is fine after this.

**EDIT**

Closing this preemptively cause I want this to be the last post on this topic. Which will make it easy for people to find the workarounds. Flag to open if still an issue after a rebuild.

---

_[View the full topic](https://meta.discourse.org/t/upgrading-from-admin-upgrade-takes-very-long/256879)._