http-status-code-504

I coded a script for database import, it makes a few jobs on database. When I work this script, after a few minutes I'm getting "504 Gateway Timeout Error". I increased all timeout values on php.ini, also I increased execution times but it is still same. You can increase maximum execution time in php. ini_set('max_execution_time', 300); //300 seconds = 5 minutes write a info file on server <?php phpinfo(); check max whats comes here if its return 0 then there is something different to do else make sure you changed on correct ini file You can check your ini file location also from phpinfo()

I have a Perl CGI application that sometimes times out, causing it to be killed by Apache and 504 Gateway Time-out error to be sent to browser. I am trying to profile this application using NYTProf, however I cannot read profile data: $ nytprofhtml -f www/cgi-local/nytprof.out Reading www/cgi-local/nytprof.out Profile data incomplete, inflate error -5 ((null)) at end of input file, perhaps the process didn't exit cleanly or the file has been truncated (refer to TROUBLESHOOTING in the documentation) I am using sigexit=1 NYTProf option. Here's minimal CGI script that reproduces problem: #!/usr

The client requested to download a compressed log file, using Ext.js a form submission on an embedded iframe . Request was sent to server, which has Apache and JBoss 6 . The servlet compresses log files, do some database operation and returns the compressed file. Exactly after 2 min, the 504 Gateway Time-out The server didn't respond in time message is seen at the browser net panel. How to fix this error? Ricardo The servlet was taking a long time to compress the log files, and Apache 's timeout was set to 2min. The error was fixed by increasing the TimeOut Directive on the httpd.conf file: #

I am using Nginx as a reverse proxy that takes requests then does a proxy_pass to get the actual web application from the upstream server running on port 8001. If I go to mywebsite.com or do a wget, I get a 504 Gateway Timeout after 60 seconds... However, if I load mywebsite.com:8001, the application loads as expected! So something is preventing Nginx from communicating with the upstream server. All this started after my hosting company reset the machine my stuff was running on, prior to that no issues whatsoever. Here's my vhosts server block: server { listen 80; server_name mywebsite.com;