ExportAction 502 Bad Gateway in Staging/Production
I upgraded to Filament 3.2 to use the new ExportAction. Awesome feature and works locally without issue.
When I push to staging/production I get a 502 Bad Gateway error. I know it's not a lot to go on, but I'm not sure what's going on. I use S3 for my file system. The file is created and I can download it if I manually go into S3. Using Vapor if that matters. Thanks!
3 Replies
Not 100% sure but it sounds like a server config issue.
Anything in the log files?
I agree. I'm just not sure where to start
There's nothing in the Vapor logs
It happens so quickly I feel like the request might not even be reaching my server
It's not a timeout error
@awcodes I'm experiencing the same issue.
1. the average execution time when requesting a pre-signed URL for a single S3 is 1s .
2. 140 files exist in my data.
3. my Nginx is set to timeout at 1 minute.
The upload component of filament puts the call to get the files into one request (even though my files exist in a different component) which causes the request to be very slow until the gateway times out.