-
-
Notifications
You must be signed in to change notification settings - Fork 819
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export of parts through admin fails with 502 Bad Gateway #5571
Comments
This may just be related to the number of items you are exporting. There are probably some improvements which could be made to make the export code faster, but I'd suggest simply increasing your timeout. Probably on your nxinx server? |
@SchrodingersGat Thank you for the reply. I am not sure how to do this. I searched with Google and it suggested nginx server instead of nxinx as you typed. From what I read a time out would return a 504 error not a 502 error. I did try to increases the time out by following the instructions outline here : https://ubiq.co/tech-blog/increase-request-timeout-nginx/ After making these changes the 502 error is still happening, Did I do the correct changes? Are there other settings I can try to adjust? |
@mattbnz @SchrodingersGat @elmo2k3 @bobek I am still experiencing this issue. I can add filter to do a smaller download and it works, so the allowed timeout makes since. I am still not sure how to increases the time out. Can anyone help me with this or point me to resources that can help me understand how to increase the timeout. |
@SparkeyinVA which file are you editing to change the timeout value? |
@SchrodingersGat I edited /etc/nginx/nginx.conf, by adding the following code. http{ After saving the conf file, then did a reboot of the server. This did not change the behavior so I have since removed the changes. |
@matmair in the context of the installer, is this: A) the file that they should be changing |
Changing the timeout there should work as long as the default nginx settings the packager ships were not touched. The setting is correct. |
This issue seems stale. Please react to show this is still important. |
Please verify that this bug has NOT been raised before.
Describe the bug*
I have a parts database with currently 731 parts. I export a few reports and merge with our Sage 50 accounting system from time to time. Three months ago I was able to export 652 parts fine. Today I am only getting 502 Bad Gateway when I try to export my parts database. Other reports have downloaded with no problem. SupplierPart, Stock Item, and BOMItem. The Supplierpart export has always been larger then the parts file.
Steps to Reproduce
This also occurs when I try to download the parts database from the regular site URL/Part/ and click download table data.
Expected behaviour
I expected the file to download.
Deployment Method
Version Information
Version Information:
InvenTree-Version: 0.12.6
Django Version: 3.2.19
Commit Hash: 942bc53
Commit Date: None
Commit Branch: stable
Database: sqlite3
Debug-Mode: False
Deployed using Docker: False
Platform: Linux-6.2.0-32-generic-x86_64-with-glibc2.35
Installer: PKG
Target: ubuntu:20.04
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.0.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}]
I am using the Quick Script install and check for updates weekly
Please verify if you can reproduce this bug on the demo site.
Relevant log output
The text was updated successfully, but these errors were encountered: