Error when attaching a document to an issue

Question

Two of my team members are getting errors when attaching documents to issues. It happens regardless of whether they browse and select a file or drag a file to attach. The error message simply reads

File "xxxx.docx" was not uploaded

I can attach documents without any problems the only difference we can tell is that I'm using win10 and they are using win7

Is anyone aware of any issues attaching documents in win7 on the new version of JIRA

Eduard M · Answer

Hi, the error you posted was obtained using IE's console, correct? I would check the following further:

1. clear the browser cache as there may be some incomplete cached response still present. Possibly try InPrivate browsing in IE as well.

2. make sure you can load the page at the URL in the error, there should be a large script present in the page

3. try first going to Edit mode before attempting the attachment.

The Atlassian Cloud Environment utilises the Amazon CloudFront CDN for caching and serving the instance with content, including how attachments are uploaded and downloaded. You should ensure your browser is hitting our CDN properly, visit the following page and make sure the IP ranges for Cloudflare are not being blocked:

* Locations and IP Address Ranges of CloudFront Edge Servers

Adam Clark_6bghbm · Answer

This was previously working, we have been using JIRA for about a year and haven't recently changed our browser either.  we are just suddenly getting this error. It looks like JIRA (cloud) has recently been updated so not sure if that's had an impact?

As mentioned previously my team are on win7 OS and i'm on Win10 we all use IE11 browser. The win7 users don't have access to another browser as its set as default by the administrator. I don't get the issue being on Win10 I can attach docs without a problem but the Win7 users all get the same issue so again not sure if this is a factor?

Do you have any further suggestions?

Eduard M · Answer

Hello, thanks for the error.

Interesting, this is not an error that I can easily locate in other cases. I'd suggest having your users try a different browser (so they wouldn't have to mess with the IE configuration) to test for this issue. If it works in other browsers, I would look at the IE configuration/settings further.