'
```
---
### Author:  [@EddieC](https://meta.discourse.org/u/EddieC)
#### Post date: [May 17, 2018, 3:43pm UTC](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713/8 "2018-05-17T15:43:47Z")
> [@fhe](#):
>
> I’ve just tried to update from Discourse 2.0.0 beta 9 to beta 10 and I’m now faced with a blank page on `/admin/upgrade` after updating docker manager.
> [@fefrei](#):
>
> I’m having the same issue. It’s an internal server error:
I’m having the very same issue.
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [May 17, 2018, 3:50pm UTC](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713/9 "2018-05-17T15:50:20Z")
@featheredtoast looks like it’s related to [your change](https://github.com/discourse/docker_manager/commit/35036dfee2dcdb96c2801f262bca478e782356c9)?
---
### Author:  [@bts](https://meta.discourse.org/u/bts)
#### Post date: [May 17, 2018, 3:55pm UTC](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713/11 "2018-05-17T15:55:16Z")
Hmm I made a topic reporting this yesterday and can’t find it now, seems it may have been deleted… 🤔
Working for me after rebuild though. (I think I had to run `./launcher rebuild app` twice for some kind of database cleanup task.)
---
### Author:  [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [May 17, 2018, 3:55pm UTC](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713/12 "2018-05-17T15:55:51Z")
Sorry about that – anyone affected by this will need to rebuild, for anyone holding off, I was depending on a newer version of discourse for the manager itself, 1 moment…
---
### Author:  [@EddieC](https://meta.discourse.org/u/EddieC)
#### Post date: [May 17, 2018, 3:58pm UTC](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713/13 "2018-05-17T15:58:39Z")
> [@featheredtoast](#):
>
> anyone affected by this will need to rebuild
I can confirm that `./launcher rebuild app` will return things to normal again.
---
### Author:  [@EddieC](https://meta.discourse.org/u/EddieC)
#### Post date: [May 17, 2018, 4:02pm UTC](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713/14 "2018-05-17T16:02:59Z")
What’s weird is that all the Discourse native plugins are gone suddenly:
---
### Author:  [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [May 17, 2018, 4:04pm UTC](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713/15 "2018-05-17T16:04:19Z")
You’re probably talking about lazyYT and discourse poll!
those are now a part of core and that is why are not displayed as a plugin.
---
### Author:  [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [May 17, 2018, 4:09pm UTC](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713/16 "2018-05-17T16:09:15Z")
That’s expected - “plugins” that are shipped with discourse aren’t really plugins (every Discourse instance has them!) so they have been removed from that page.
---
### Author:  [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [May 17, 2018, 4:14pm UTC](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713/17 "2018-05-17T16:14:28Z")
Fixed here: [FIX: support listing plugins for older discourse versions · discourse/docker\_manager@c00d6d1 · GitHub](https://github.com/discourse/docker_manager/commit/c00d6d10f0abffbe64e6aac1cadf73fca96bb68e)
Anyone else updating discourse will not hit this anymore.
---
### Author:  [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [May 19, 2018, 1:00am UTC](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713/18 "2018-05-19T01:00:01Z")
This topic was automatically closed after 32 hours. New replies are no longer allowed.