Stash Support Plugin -> 3.5 Caused 500 Error?

The most recent plugin upgrade of Stash Support Plugin caused all repositories to have a 500 error on the browse screen. I've tested this in two environments. Stash had to be stopped and restarted which disrupted business.

3 answers

Hi Jen,

That error likely indicates that the plugin failed to startup again after being upgraded. If the problem is persisting after restarting, I'd recommend contacting support at, as we'll need version numbers and possibly logs to diagnose what's going wrong.



Thanks Tim. I believe you are correct - I opened a ticket to support to check the error.

0 vote

It appears that the problem occurred due to the database being unavailable for a period of time and not to a specific plugin. The cause is described in more details on

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,762 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you