Yes, there are official guides for upgrading the GrowthBook application version of a self-hosted instance. The process is generally straightforward and designed to be smooth. Here are the key points: 1. The recommended method for updating is to use the

latest

Docker image tag. This ensures you get the most recent stable build with all bug fixes and features [FAQ](https://docs.growthbook.io/faq#which-docker-image-tag-should-i-use-when-self-hosting). 2. To update your self-hosted GrowthBook instance, you can use the following commands:

bash docker-compose pull docker-compose up -d

This will pull the latest image and restart the container with the updated version [Self Hosting GrowthBook](https://docs.growthbook.io/self-host#updating-to-latest). 3. GrowthBook updates are designed to be backward compatible, so you can usually apply them with a single command [Using > Security > Self-hosted deployments](https://docs.growthbook.io/using/security#self-hosted-deployments). 4. It's important to note that while upgrading is generally smooth, there might be significant changes between versions. However, the GrowthBook team ensures that the upgrade path remains smooth [Forum Conversation](https://linen.growthbook.io/t/15652733/hey-guys-first-i-need-to-thank-you-for-the-growthbook-and-co). 5. When upgrading, make sure your MongoDB container's volumes are properly defined to avoid data loss [Forum Conversation](https://linen.growthbook.io/t/15652733/hey-guys-first-i-need-to-thank-you-for-the-growthbook-and-co). It's recommended to regularly update your self-hosted GrowthBook instance to ensure you have the latest features and security patches.

Yes, some users have reported experiencing issues when upgrading GrowthBook. Here are a few examples from the knowledge sources: 1. One user encountered an "OAuth Error: Error Signing In" after upgrading to version 2.7. However, this was later found to be due to an incompatible Azure configuration of the redirectURIs, rather than a problem with GrowthBook itself [Github Issue](https://github.com/growthbook/growthbook/issues/2099). 2. Another user reported issues with the Features UI after upgrading from v1.8.0 to v3.2.0. When trying to view feature configurations, they encountered an error. This might be related to changes in database queries that are not compatible with their MongoDB API for Cosmos DB setup [Forum Conversation](https://linen.growthbook.io/t/23152366/hi-all-we-self-host-growthbook-in-azure-we-currently-use-an-). 3. Some users have experienced "failed to fetch" errors when trying to edit something in the GrowthBook dashboard. This issue seems to be related to CORS configuration, especially in self-hosted setups [Forum Conversation](https://linen.growthbook.io/t/16149977/hi-can-someone-help-me-why-i-get-this-message-failed-to-fetc). 4. One enterprise user reported being unable to log in after upgrading, getting stuck on the loading page [Forum Conversation](https://linen.growthbook.io/t/22885070/hey-team-after-upgrading-to-enterprise-we-are-unable-to-logi). Despite these reported issues, it's important to note that the GrowthBook team strives to make upgrades as smooth as possible. They ensure backward compatibility and provide support for users experiencing difficulties. Many users have also reported successful upgrades without any issues [Forum Conversation](https://linen.growthbook.io/t/15652733/hey-guys-first-i-need-to-thank-you-for-the-growthbook-and-co). To minimize potential issues, it's recommended to: 1. Always check the release notes before upgrading 2. Test the new version in a non-production environment first 3. Ensure proper configuration, especially for self-hosted setups 4. Keep your GrowthBook instance up-to-date to benefit from the latest bug fixes and features