Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Data Provider refresh failed with error code 414

We are getting an error in the Jira log every five minutes stating a failure when trying to refresh data. I'm not certain what area of the service it is affecting, but I would like to get this figured out regardless. I've attached a screenshot of the log lines for easier reading.

I've already followed the steps in this article explaining how to increase the max URI size when using apache as a proxy, and while we are using Nginx instead of apache, increasing the URI size in Nginx didn't seem to help.

If anyone has any idea as to what could be happening, that would be helpful.


Thank you.

Screen Shot 2020-02-19 at 3.14.21 PM.png

1 answer

1 accepted

I found the answer using the workarounds listed in this open Jira ticket.

Due to large request size Jira receives error 400 from Bitbucket when refreshing dev panel cache 

Hi Anthony. 

Did it work for error code 414 in jira 

Data Provider [Id: xxxxxx, Type: stash] refresh failed with error code 414 and message - HTTP status 414 Request-URI Too Large

Suggest an answer

Log in or Sign up to answer

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you