Cannot attach file : Unable to communicate with JIRA.

I am trying to attach a very small file about 15KB and it gives the above error while trying to attach during issue create in Firefox. we are running 5.1.6.

The same seems to work in Firefox for files < 10KB and it works for all sizes in IE.

Any help is greatly appreciated.

TIA

Siva

5 answers

1 accepted

This widget could not be displayed.

The issue was found to be in the proxy server settings which was fixed and the issue was resolved.

This widget could not be displayed.

I've had the sam problem when the filename inlcluded symbols like 'ä', 'ö' or 'ü'. Maybe you have a similar issue

This widget could not be displayed.

I have tha same probLEM in JIRA 6.3

This widget could not be displayed.

I got this error when I tried to upload a file the computer couldn't read wink  It was listed thus

-rw-------  1 root root      4390 23.01.2015 14:13 iostat.xml

So the directory could list it but not read it.  

This widget could not be displayed.

I am getting the same issue. Seems to be a problem with apache that is proxying JIRA.

As when reaching directly through http(s)://<jira_server_ip>:jira_port then attaching works fine.

At the same time on the catalina.out I am getting:

2015-08-12 11:39:46,280 http-bio-8080-exec-25 WARN username1 699x24x2 z5fvv7 10.xxx.xxx.xxx /secure/AttachFile!default.jspa [webwork.view.taglib.IteratorTag] Value is null! Returning an empty set.
.
.
.
2015-08-12 11:41:10,841 http-bio-8080-exec-22 WARN username2 701x80x1 4jc6zh 10.xxx.xxx.xxx /secure/AttachFile!default.jspa [webwork.view.taglib.IteratorTag] Value is null! Returning an empty set.
2015-08-12 12:03:24,196 http-bio-8080-exec-6 WARN username2 723x612x1 1asgak8 10.xxx.xxx.xxx,127.0.0.1 /secure/AttachFile!default.jspa [webwork.view.taglib.IteratorTag] Value is null! Returning an empty set.

 

JIRA 6.3.6 / jre1.8.0_40

Managed to solved that. The problem was not-related to JIRA actually. There was a DNS issue which resulted in JIRA not being able to resolve the FQDN of the virtual host. For the history, the messages on apache were like: {code} ... [Wed Aug 12 14:55:35 2015] [error] (104)Connection reset by peer: proxy: prefetch request body failed to 127.0.0.1:8080 (localhost) from 10.xxx.xxx.xxx () [Wed Aug 12 14:58:41 2015] [error] (104)Connection reset by peer: proxy: prefetch request body failed to 127.0.0.1:8080 (localhost) from 10.xxx.xxx.xxx () [Wed Aug 12 14:58:46 2015] [error] (104)Connection reset by peer: proxy: prefetch request body failed to 127.0.0.1:8080 (localhost) from 10.xxx.xxx.xxx () [Wed Aug 12 14:59:10 2015] [error] (104)Connection reset by peer: proxy: prefetch request body failed to 127.0.0.1:8080 (localhost) from 10.xxx.xxx.xxx () {code}

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

106 views 2 0
Join discussion

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