coolify: [Bug]: 504 Gateway Time-out when updating application general configuration

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)

  • Create a new project from public git repository: https://github.com/photogabble/website/
  • Update to use the release/2024 branch (as this has the new Dockerfile)
  • Deploy
  • Realise that its defaulted to port 3000 on creation and update it to port 80, click save and wait for the 504 Gateway Time-out

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

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 9
  • Comments: 27 (2 by maintainers)

Most upvoted comments

Same here. When I’m trying to build my next js app

I’m on self hosted, on a 16-core dedicated server.

Have since restarted the coolify containers and still getting the same thing happen: image

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;
    }
});

@orenaksakal I have exactly the same problem with Hetzner Firewall. I solved it by enabling all TCP and UDP outgoing traffic. Check you have UDP enabled to the outside too!

for me adding swap didn’t help but disabling hetzner firewall works I already allow all realtime ports in that firewall but when enabled it 504s. I keep ufw and disable hetzner firewall to overcome this problem