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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unknown Server Error (200) when using CSV Import

Multiple people on my team are trying to import issues in different projects using the External System Import feature and are getting the error: 

Unknown Server Error 200.pngThe functionality was working last week just fine, but we have not been able to use it this week.

2 answers

For what it's worth, when a user encounters this issue, I have them do a Shift+Refresh before uploading the attachment again.


0 votes
Rodrigo B_ Atlassian Team Sep 16, 2021

Hi @Benjamin Kister

I know it's been a long while, but for the sake of all people that find this question in the future, here is a diagnosis of mine for this problem:

Looking at the HTTP request sent by the browser to upload the file, which uses the endpoint "/rest/jira-importers-plugin/1.0/AttachTemporaryFile", I noticed the HTTP response was coming as a 200, when in fact, it should be a 201, because an upload was made, and that's how our server responds to it.

That was intriguing, why was our server answering the same procedure in different ways? So I looked up our own backend logs, and absolutely nothing was there for this call, we did not answer this.

Back to the HTTP request's response, the remote IP address was a 10.x.x.x, this is reserved for private networks, which means the answer came from the same local network. Now scroll down to the HTTP response headers and voilá, a host name, and none of our Atlassian headers, the actor was a middleware that scans requests before sending to the internet (to our server).

It turns out this middleware blocked the request, but answered to the end user's browser as a 200, as if nothing wrong happened, breaking the CSV upload experience, because it actually never happened.


Rodrigo Becker

Cloud Enterprise Support Engineer

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events