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 votes

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
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

679 views 5 9
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