504 Gateway Timeout

Have you tried restarting php5-fpm?

sudo service php5-fpm restart

doesn't help .. :( i've rebooted the server, rebooted nginx, but nothing helps ..

The socket will only be there if php5-fpm creates it, maybe your config became messed up. Not sure why it would randomly do it though, never happened to me.

/etc/php5/fpm/pool.d/www.conf

Found It! The site depends on the data from an API and the API call has a 504 timeout. Maybe i have to check my code to prevent this :(

I had the same issue. The problem was due to the invalid database host name. Hope this might be helpful to someone.

My 504 timeout problem was due to not having a mail package installed for my WordPress plugins. This may be solved in newer forge installations but for older instances you can find my answer here:

https://laracasts.com/discuss/channels/forge/504-timeout-on-form-submissions-through-wordpress-on-laravel-forge-server

$ sudo nano /etc/php/7.0/fpm/php.ini

max_execution_time = 600

$ sudo nano /etc/php/7.0/fpm/pool.d/www.conf

request_terminate_timeout = 600

$ sudo /etc/nginx/sites-available/midominio.dev

location ~ .php$ { fastcgi_split_path_info ^(.+.php)(/.+)$; fastcgi_pass unix:/var/run/php/php7.0-fpm.sock; fastcgi_index index.php; include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_intercept_errors off; fastcgi_buffer_size 16k; fastcgi_buffers 4 16k; fastcgi_connect_timeout 600; fastcgi_send_timeout 600; fastcgi_read_timeout 600; }

If you are able to debug your way through, you might find the source of the problem relatively easily. For me, a dd(); would trigger before but not after a model query, which made me realise MySQL was the issue. Since it was installed via brew, I just ran brew services restart mysql to resolve it.