Error Message and Logs
A public application remained unreachable with HTTP 502 after its exposed port was changed from the default 80 to the container's actual listening port 9000.
The application container itself was healthy and listening on 9000, but the effective Traefik label still targeted port 80:
traefik.http.services.<service>.loadbalancer.server.port=80
Updating the exposed-port setting and force-deploying did not reconcile the label to 9000. Correcting the routing label and force-deploying restored the public endpoint.
This may be related to #10546, but the symptom is different: in this case the load-balancer label existed and pointed to a stale port, rather than the HTTP service label being absent.
Steps to Reproduce
- Create an application whose container listens on port
9000.
- Assign a public domain while the application's exposed port is absent or still defaults to
80.
- Deploy and confirm the application container is healthy but the public domain returns 502.
- Change the exposed port to
9000 through the application settings/API.
- Force-deploy the application.
- Inspect the container's generated Traefik labels.
Expected Behavior
Changing the exposed port should invalidate and regenerate all related proxy labels. After deployment, Traefik should target port 9000 and the public domain should work.
Actual Behavior
The saved application setting showed the new exposed port, but Traefik continued routing to port 80. The healthy application remained unavailable until the routing label was corrected separately.
Example Repository URL
No response — reproduced with a managed MinIO application listening on port 9000.
Coolify Version
v4.1.2
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 24.04; Docker 29.5.3
Additional Information
Suggested regression test:
- Generate labels for an application with exposed port
80.
- Update
ports_exposes to 9000.
- Re-run configuration/deployment reconciliation.
- Assert that no generated Traefik service label still targets
80 and that the effective label targets 9000.
Observed during a production migration. No credentials, domains, resource UUIDs, or customer data are included in this report.
Error Message and Logs
A public application remained unreachable with HTTP 502 after its exposed port was changed from the default
80to the container's actual listening port9000.The application container itself was healthy and listening on
9000, but the effective Traefik label still targeted port80:Updating the exposed-port setting and force-deploying did not reconcile the label to
9000. Correcting the routing label and force-deploying restored the public endpoint.This may be related to #10546, but the symptom is different: in this case the load-balancer label existed and pointed to a stale port, rather than the HTTP service label being absent.
Steps to Reproduce
9000.80.9000through the application settings/API.Expected Behavior
Changing the exposed port should invalidate and regenerate all related proxy labels. After deployment, Traefik should target port
9000and the public domain should work.Actual Behavior
The saved application setting showed the new exposed port, but Traefik continued routing to port
80. The healthy application remained unavailable until the routing label was corrected separately.Example Repository URL
No response — reproduced with a managed MinIO application listening on port
9000.Coolify Version
v4.1.2
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 24.04; Docker 29.5.3
Additional Information
Suggested regression test:
80.ports_exposesto9000.80and that the effective label targets9000.Observed during a production migration. No credentials, domains, resource UUIDs, or customer data are included in this report.