We have been testing file uploads to a server which has a requirement for large (~2 GB) attachments. In the process it was discovered that files greater than ~500 MB in size fail to upload from remote clients even though locally uploaded files are received without error for sizes up to ~1 GB (the largest tested so far).
The server is located behind an Nginx reverse proxy which has been configured to permit large files and long transfer times in case the remote client is on a slow or problematic connection.
As mentioned above, the uploads do succeed if they originate on the server or on the local area network of the server, and they do also arrive from a remote client if the file size is less than ~600 MB (test files increment in units of 100 MB).
Variable NC_ATTACHMENT_FIELD_SIZE has been set to ~2 GB for testing and appears to be working judging from its default value (20 MiB) and the size of the test files.
When a failure does occur the upload window vanishes and an error is reported:
“Request failed with status code 408”
No errors are reported in the Nginx logs.
What is code 408?
Is there anything we need to do on the server side to further configure it for large file uploads?
The HTTP 408 Request Timeout error indicates that a request to a website server took longer than the server was prepared to wait. This means that the connection with the website has “timed out”.
See if there is something that you can fiddle on the nginix.
hey @HG2S, it would help immensely if you can share the snippet here in the reply. That way, any community member landing on this post can benefit from it.
The following Nginx configuration should help NocoDB users integrate the database with an Nginx reverse proxy.
• Please note that in this case the proxy is co-located with the NocoDB server.
• The design is meant to support remote clients with big files on so-so connections.
• Users should customize settings such as timers, buffers and domain names as needed.
The configuration was evaluated by Security Headers and Mozilla HTTP Observatory and received grades of A+ and B, respectively. That said, further work needs to be done to refine the Content Security Policy (CSP).
Please post questions, comments, improvements and alternative approaches. We are new-comers to NocoDB and are still going up the learning curve.