Internal Error, please contact system administrator

[Steven Camilleri]

Hi All,

We currently have our JIRA instance (Server-Core) hosted on AWS. For some reason, whenever someone uploads something .jpeg, .png, .mp4 etc. that is about 10mb or equivalent. It fails. We have an NGINX proxy which is set to unlimited and on JIRA it is set to 2GB but it still fails.

I have searched numerous searches on here and Google, but I can't find a definite answer. I had previously contacted Atlassian Support, but they wanted a copy of our JIRA, which a bit much if you ask me just to troubleshoot this issue.

Anyone with a similar setup as myself, can provide any insight? Keep in mind it is hosted on AWS using the server core option.

[Nic Brough -Adaptavist-]

We'll need to see the logs for the time at which the errors occur.

[Steven Camilleri]

There is nothing useful in the logs. Something similar to this, but running on NGINX proxy: https://confluence.atlassian.com/jirakb/unable-to-upload-large-attachment-even-when-attachment-file-size-limit-exceeds-it-815242350.html

[Steven Camilleri]

I also noticed any file that is 5mb or less uploads fine.

[Steven Camilleri]

It seems somehow NGINX is still preventing it. Getting Error Code: 413 in console mode from the browser.

[Nic Brough -Adaptavist-]

Ok, that makes sense.  A 413 error means "whatever the http(s) stream we are handling, it is too big".  Most browsers do not have any code to do capping that would cause a 413, but web-servers all do, and most set a limit by default (to prevent load and overloading attacks by default)

Your nginx server is the culprit here, it's got a cap (presumably of 5Mb) on uploads.  You'll need to increase that cap.

[Tom Lister]

This Hi @Steven Camilleri

try going to cog/General Configuration and editing the Attachment Maximum Size

also check NGINX limits

https://www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-large/