We have a single on-premise installation which is giving us a Http 504: Bad Gateway error message in the browser console when I attempt to use the AsyncUpload control. We are using this in a web farm, the web.config file contains the same values in each of the web servers in the farm:
- Telerik.AsyncUpload.TemporaryFolder
- Telerik.AsyncUpload.ConfigurationEncryptionKey
- Telerik.Upload.ConfigurationHashKey
- <configuration><system.web><machineKey>
All other installations are fine, but this is not. The temporary upload path shows that the file is uploaded with the ".tmp" extension for every attempt, the upload control shows the file is uploaded and the "remove" button is visible, but the page does not interact with the uploaded file.
Can anyone help us understand why this is occurring? Any ideas where to check next? Thanks.
1 Answer, 1 is accepted
Can you please double check you have performed all the mandatory steps in the following article: Web Farm and Load Balancing?
The Windows user account that the ApplicationPool uses must have permissions to read and write to these folders. Setting the UseApplicationPoolImpersonation property to true instructs the control to impersonate the application pool.
If files do not get written at all to the target folder, try giving Everyone permissions to the TargetFolder and TemporaryFolder. If this resolves the issue, then you need to locate the user that IIS operates under, and provide them with sufficient privileges. Set the UseApplicationPoolImpersonation property of the RadAsyncUpload to true.
Such a shared drive can be considered a single point of failure, which is something load balancing and web farms strive to avoid. If this is a concern in your use case, set DisableChunkUpload to true so that the files will be uploaded in one piece and use a custom upload handler to store them according to your application requirements.
Best Regards,
Rumen
Progress Telerik