Open carbontwelve opened 1 month ago
I cannot reproduce the issue. Are you using the cloud version?
I'm on self hosted, on a 16-core dedicated server.
Have since restarted the coolify containers and still getting the same thing happen:
It's a 504 in response to a post request made to /livewire/update
after 60 seconds. I have attached a shell to the coolify container and see nothing pop into the laravel.log
so I believe it's taking longer to process the update than the 60 second timeout set in nginx.
As an aside, it might be a good idea to add handling for this error:
Livewire.onError((message, statusCode) => {
if (statusCode == 504) {
// Handle the timeout here, then return false
return false;
}
});
I've got this issue too on selfhosted version.
same here when trying to stop the appwrite stack
Same here. When I'm trying to build my next js app
Add a swapfile resolved my issue.
https://support.hostinger.com/en/articles/8124185-how-to-set-up-swap-on-hostinger-vps
I believe #3220 is related to this issue.
I am also struggling with the exact same issue and trying to diagnose this. Specifically in the default localhost instance
Description
I have a public git repository that is using the Dockerfile buildpack. When editing any of the general configuration values, upon pressing save, after a while a full page modal pops up with
504 Gateway Time-out
error.Minimal Reproduction (if possible, example repository)
release/2024
branch (as this has the new Dockerfile)I then reload the page and see the
The latest configuration has not been applied
toast, so the configuration change was made.Exception or Error
No response
Version
v4.0.0-beta.315