[Bug]: Traefik not restarting when using the "Restart Proxy" button (remote server)

[nuxwin]

Description

When adding a remote server, restarting of the proxy doesn't seem to work when using the "restart" button. We need to stop the proxy, then start it again as workaround.

Minimal Reproduction (if possible, example repository)

Setup a remote server via the Coolify UI. Once done, try to restart the proxy using the provided "restart" button.

Exception or Error

Docker container is stopped but is never coming up back

Version

4.0.0-beta.302 (next image)

Cloud?

• [ ] Yes
• [X] No

[andrasbacsai]

Please do not use the next image if you are not jut playing around, I change it very often - every day (like I changed a migration today, so you could end up using a wrong database layout).

I cannot reproduce the issue. Do you have any error shown?

[nuxwin]

@andrasbacsai I use it as playground, don't worry. The bug is still relevant on the last released version ;) Want just help you a bit.

Edit: I'll try to provide you with more information.

[nuxwin]

@andrasbacsai I can still reproduce the problem with latest released version. There is no logs available.

Context : Secondary server (remote), not the one which host Coolify.

Steps:

1. Through the Coolify UI, for the secondary server, 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 a 504 Gateway Time-out error (see the first screen below).

[biboc]

When using restart, it does stop correctly coolify-proxy so port 80, 443, 8080 are kept opened by docker-proxy and you can't start it anymore I stop and rm coolify-proxy then I killed manually docker-proxy processus listenning to previous mentionned ports then restart docker to make it work again