Compose service domain may keep returning 502 until the domain is deleted and recreated

To Reproduce

Problem

A domain attached to a Docker Compose sub-service may return 502 Bad Gateway even though the target container is healthy and the app responds correctly on the configured internal port.

A normal redeploy does not always fix it.

What fixes it reliably is:

1. delete the domain in Dokploy
2. create the same domain again
3. redeploy / refresh routing

Expected

If a Compose sub-service is healthy and the domain points to the correct internal port, redeploy should be enough.

Deleting and recreating the domain should not be required.

Actual

• container is up
• service responds correctly inside the container
• public domain still returns 502

Current vs. Expected behavior

Example:

docker exec <container> sh -lc 'wget -qO- http://127.0.0.1:8080/healthz'
{"status":"ok"}

curl -fsS https://<domain>/healthz
curl: (22) The requested URL returned error: 502

### Provide environment information

```bash
ubuntu 24.04
Dokploy Version v0.28.4
Compose App

Which area(s) are affected? (Select all that apply)

Application

Are you deploying the applications where Dokploy is installed or on a remote server?

Remote server

Additional context

No response

Will you send a PR to fix it?

Yes

No files or tests are named. Reproduce the failure with a Docker Compose sub-service, a healthy internal health endpoint, and a domain returning 502; then trace the domain and redeploy routing path. Done means redeploying updates routing so the domain works without deleting and recreating it.