Cannot attach file ****.pdf: Unknown server error (413).

[Alexandr Dorogikh]

Hi

Plugin unable to attach file to the project if file size larger than 1 MB.

The limit is set to 20 MB.

What's can be wrong?

[Alexandr Dorogikh · Accepted solution]

That was our fault - the problem is in nginx configuration.

[Scott Reynolds]

While you didn't post the answer here, I assume that it was simply setting client_max_body_size in your nginx config. That certainly solved things for us.

[Gabriel Ajabahian]

We had the same problem when we moved the system from Windows to Centos with nginx, to resolve it just edit your nginx.conf file which should be somewhere here:

/etc/nginx/nginx.conf

In the http section add the client max body size

client_max_body_size 10M;

If you have more websites running, you can also add this in your jira conf or confluence config file.

Regards

[Alexandr Dorogikh]

jira logs

http://www.ex.ua/view_storage/179316926562

[Alexandr Dorogikh]

access.log does not contain any plugin exception info

[Danut M _StonikByte_]

Hi Alexandr!

Please report this on the Bitbucket repository of Documents:

https://bitbucket.org/StonikByte/documents-add-on/issues?status=new&status=open

Then someone from support will get in touch with you.

Thank you,

Danut.

[twong_atlassian]

Could it be possible that a network applicance or proxy server could be throwing the 413? Can you verify the presence of either of those? Could yo hit the machine via localhost direct to port and try the same operation?

[Alexandr Dorogikh]

I am about this

[Luis Mayora]

may be the log from the tomcat logs directory /<jira-installation-dir>/logs. You will find a lot of logs there like access.log, etc

[Alexandr Dorogikh]

How/where can I get exception details?

log/atlassian-jira.log does not contain any similar to plugin exception information.

[Luis Mayora]

Can you post the exception details?