File too large (File Upload Test)

Peter Truong

unread,

Feb 5, 2026, 10:08:01 AM (9 days ago) Feb 5

to QATrack+

Hello there,

First time running into this problem when uploading zipped CT Catphan images for Pylinac analysis. This particular imaging mode/protocol has a smaller slice thickness, which causes about double the amount of images. As a consequence, the zipped file of around 46 MB in comparison to the 23 MB of other imaging protocols flags an error indicating "File too large - You may need to increase the maximum request size on your server" (refer to attached image below). With this error, analysis does not progress/process. QATrack Import - File Too Large.PNG

I did find a conversation with a potential solution, but it is for the Linux - apache configuration, which is contrary for our current setup (or at least our IT indicates that our server was not installed with apache nor nginx). Had a look into our local_settings.py, but no success in finding a parameter relevant for server upload size limites that could be changed. So, I am wondering if anyone has experienced this/has a solution for the Windows configuration (current version: QATrack+ v3.1.1.3)?
Thanks in advance!

Cheers,
Peter

Rafael Segovia

unread,

Feb 5, 2026, 10:13:12 AM (9 days ago) Feb 5

to Peter Truong, QATrack+

Hey!

We had the same issue. I’ve just forwarded you the answer we got from Randle. Maybe it goes to spam, so check there just in case.

Regards,

Rafa

--
You received this message because you are subscribed to the Google Groups "QATrack+" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qatrack+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/qatrack/f629951b-326a-4b62-bad8-47146df28360n%40googlegroups.com.

Peter Truong

unread,

Feb 5, 2026, 11:02:36 AM (9 days ago) Feb 5

to QATrack+

Hello Rafael,

Thank you for your response. So, I did have a look at your referenced issue before/solution from Randle, but I didn't quite follow if tests/zipped files were being uploaded in a QATrack test/web-interface or from another method as I do not see the same error/status codes (400, 200, 500 etc.). I am also unsure if the fix is available/applicable from linux (your configuration) server to ours (assuming Windows - though honestly, not too sure anymore at this point).

Anyways, on my side, I was able to find a few more conversations with updated keyword ("size limit") and I found promising results (will post outcome after IT intervention):
IIS/SQL Limit
Subsequent update to qa.js (if needed)

Cheers,
Peter

Peter Truong

unread,

Feb 9, 2026, 12:33:24 PM (5 days ago) Feb 9

to QATrack+

Hello there,

Just an update to the information from our IT and document the outcome of the fixes on their end:
SQL Server 2019 is what our database/QATrack is utilizing.

I forwarded the same link that Randle had provided with emphasis on following Option 2: https://www.inflectra.com/support/knowledgebase/kb306.aspx

IT reported back to me and stated that limit was raised to 300 MB.
Tested on our development version of QATrack, and all seems to be functional for our 46 MB zipped folder upload.

Cheers,
Peter

msmor...@gmail.com

unread,

Feb 11, 2026, 5:50:04 AM (3 days ago) Feb 11

to QATrack+

Hello,

We had the same problem, and increased the maxAllowedContentLength, but then immediately received the following error:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/> <title>502 - Web server received an invalid response while acting as a gateway or proxy server.</title> <style type="text/css">  </style> </head> <body> <div id="header"><h1>Server Error</h1></div> <div id="content"> <div class="content-container"><fieldset> <h2>502 - Web server received an invalid response while acting as a gateway or proxy server.</h2> <h3>There is a problem with the page you are looking for, and it cannot be displayed. When the Web server (while acting as a gateway or proxy) contacted the upstream content server, it received an invalid response from the content server.</h3> </fieldset></div> </div> </body> </html>

Anyone have any ideas how to deal with that error?

Reply all

Reply to author

Forward