Description and Error Message
When using Docker Compose applications with services that listen on non-standard ports (e.g. 3000, 3001), the domain configuration correctly requires the port so the proxy knows where to route traffic:
https://example.com:3000
https://example.com:3001/backend
According to the official documentation :
The port here only tells Coolify where to send traffic within the container; the proxy will make this service available on the normal port (http://example.com port 80/443).
However, the automatic comment that Coolify posts on GitHub Pull Requests includes the internal port in the links:
https://136.example.com:3000
https://136.example.com:3001/backend
Expected Behavior
The links in the PR comment should be cleaned of the internal port, e.g.:
https://136.example.com
https://136.example.com/backend
Steps to Reproduce
- Create a Docker Compose application in Coolify with at least one service that listens on a non-standard port (e.g.
3000 or 3001).
- In the domain configuration for that service, include the port (as required by the documentation), for example:
https://myapp.example.com:3000https://myapp.example.com:3001/backend
- Enable Preview Deployments and set a URL template (e.g.
{{pr_id}}.{{domain}}).
- Open a Pull Request against the configured branch.
- Wait for the preview deployment to finish.
- Check the automatic comment that Coolify posts on the PR.
Example Repository URL
No response
Coolify Version
v4.1.2
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Screenshots / Visuals
No response
Additional Information
Suggested fix
Update getPreviewLinks() in ApplicationPullRequestUpdateJob.php to clean the domains before generating the Markdown links using getFqdnWithoutPort() defined in shared.php
Description and Error Message
When using Docker Compose applications with services that listen on non-standard ports (e.g. 3000, 3001), the domain configuration correctly requires the port so the proxy knows where to route traffic:
According to the official documentation :
However, the automatic comment that Coolify posts on GitHub Pull Requests includes the internal port in the links:
Expected Behavior
The links in the PR comment should be cleaned of the internal port, e.g.:
Steps to Reproduce
3000or3001).https://myapp.example.com:3000https://myapp.example.com:3001/backend{{pr_id}}.{{domain}}).Example Repository URL
No response
Coolify Version
v4.1.2
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Screenshots / Visuals
No response
Additional Information
Suggested fix
Update
getPreviewLinks()inApplicationPullRequestUpdateJob.phpto clean the domains before generating the Markdown links usinggetFqdnWithoutPort()defined inshared.php