Bitbucket throws 500 errors on startup after upgrade
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Bitbucket throws 500 errors on startup after the upgrade process.
Environment
Bitbucket Server/DC with plugins installed
Diagnosis
The logs show the following errors
1
2
2022-05-02 13:24:03,981 ERROR [http-nio-7991-exec-2] o.a.c.c.C.[Tomcat].[localhost] Exception Processing ErrorPage[errorCode=500, location=/mvc/error500]
javax.servlet.ServletException: Filter execution threw an exceptionCause
The stack trace means that a third-party plugin that's been installed is causing a conflict with the new Bitbucket version.
Solution
Try moving any installed plugins from theinstalled-pluginsfolder on the application server. The directory should be $BITBUCKET_HOME/shared/plugins/installed-plugins. Once you're in that directory - you should find any installed plugins. After you stop Bitbucket Server, if you move the plugins' jar files out of this directory, it should prevent the plugin from processing when you start Bitbucket server back up.
Then, after starting the application, re-install the proper version of the plugin(s) through Bitbucket UI.
Was this helpful?