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.
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 https://support.atlassian.com, as we'll need version numbers and possibly logs to diagnose what's going wrong.
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 https://confluence.atlassian.com/display/STASHKB/Random+500+errors+when+running+Stash+-+Database+connection+timeouts
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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 ...
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!
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