[Bug]: Traefik proxy docker compose configuration file overidden when revalidating the server

[nuxwin]

Description

We have modified the docker compose for the Traefik proxy (the one of a remote server). When we revalidate the server, the file is overriden. We should have a option to prevent reset of the modifications. For instance, we have updated the conffile to use the latest traefik version v3.1 (which seem to work very well with coolify).

Minimal Reproduction (if possible, example repository)

Add a remote server via the Coolify UI. Validate it. Modify the proxy configuration (docker compose) via the UI Revalidate the server

Exception or Error

The modifications are lost. The docker compose conffile is being fully rewritten.

Version

4.0.0-beta.320 (next image)

Cloud?

• [ ] Yes
• [X] No

[andrasbacsai]

I could not reproduce this issue.

If the compose file already exists on the server in /data/coolify/proxy/..., it will be reused on revalidation.

There are two ways to revalidate the server. One is when the server is running fine, but you still revalidate manually, and the other is when the connection is lost. Which one are you referring to?

[nuxwin]

The problem occurs when the proxy don't restart after a manual restart trigger (via the related button). So, clicking on the Revalidate server override the file. I'll retry and provide you with the exact steps and screenshot but first, I'll switch back to latest released version, downgrading my Laravel db schema via artisan if needed. Thank you for your time.

[nuxwin]

@andrasbacsai Ok, I did switched back to latest released version and I cannot longer reproduce the bug too. The problem occured in specific context as described now:

Context: A secondary server

Steps:

1. Through the Coolify UI, trigger a restart of the proxy by clicking on the provided "Restart Proxy "button, in the proxy tab. The server won't restart and you'll end with an 504 Gateway Time-out error (see the screenshot below).
2. In the "General" tab, click on the "Revalidate server" button. The server will be up again (traefik proxy).
3. Look at the Traefik configuration through the UI for the secondary server. You'll see that the configuration has been reseted back to the default. (no longer the case since I switched back to latest released version).

Below, I still post the screen about the proxy restart problem. I've no further information as the logs directory still empty.