# Upgrade discourse fails from 3.3.0 beta1 to beta2 via admin panel **URL:** https://meta.discourse.org/t/upgrade-discourse-fails-from-3-3-0-beta1-to-beta2-via-admin-panel/308038 **Category:** Self-hosting **Created:** [May 15, 2024, 6:07am UTC](https://meta.discourse.org/t/upgrade-discourse-fails-from-3-3-0-beta1-to-beta2-via-admin-panel/308038 "2024-05-15T06:07:44Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![RBoy](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@RBoy](https://meta.discourse.org/u/RBoy) #### Post date: [May 15, 2024, 6:28am UTC](https://meta.discourse.org/t/upgrade-discourse-fails-from-3-3-0-beta1-to-beta2-via-admin-panel/308038/2 "2024-05-15T06:28:10Z")
The solution appears to be to manually rebuild the image from the cli via `./launcher rebuild app`. > [@Upgrade / Rebuilds Fail due to MaxMind DB EOL](https://meta.discourse.org/t/upgrade-rebuilds-fail-due-to-maxmind-db-eol/137387/23): > > We now support the officially supported way of obtaining databases per: [https://github.com/discourse/discourse/commit/a8ffb6949c76ea16e96ec4d45e6524cd8cc42c2d](https://github.com/discourse/discourse/commit/a8ffb6949c76ea16e96ec4d45e6524cd8cc42c2d) If you wish to get regular MaxMind updates you will have to head to [GeoLite sign up | MaxMind](https://www.maxmind.com/en/geolite2/signup) to register an account and generate a license key. Then you would amend your container to include it in the env: section: env: DISCOURSE\_MAXMIND\_LICENSE\_KEY: ...key here... The fix ensures there is no time bomb anymore. If we have no lice… Don’t know why it would throw a MaxMind error while upgrading docker\_manager via the web admin console (from 3.3.0 beta1 to 3.3.0 beta2-dev) but works via the CLI. Maybe there needs to be check via the web console upgrade docker\_manager to not upgrade MaxMind until the dependencies are updated? --- _[View the full topic](https://meta.discourse.org/t/upgrade-discourse-fails-from-3-3-0-beta1-to-beta2-via-admin-panel/308038)._