[Bug]: Custom domain not working for pre-made resources like PostgreSQL

[noahsmiths]

Error Message and Logs

Proxy: Caddy (switched from Traefik)

I've added a custom domain to coolify, both with a route pointing to coolify itself and a wildcard subdomain for any deployed resources. When spinning up an app from github or a dockerfile, coolify uses the wildcard domain properly and I can see the configured routing labels via the General > Network section. However, when deploying premade templates like Postgresql, the subdomain isn't used at all when making it publicly available, and there are no options to configure the routing as there is no Network section with visible labels.

Steps to Reproduce

1. Make sure your domain is configured properly with the wildcard DNS
2. Create a new resource and choose PostgreSQL. You'll see there are no network settings that allow viewing/changing of labels, and further if you enable it to be publicly accessible under the General settings, it uses the direct IP address instead of a subdomain.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.389

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04

Additional Information

No response

[djsisson]

@noahsmiths the proxy is only setup to proxy http traffic, postgres uses tcp so does not go through the proxy

if you want to restrict the database to a subdomain, you will need to manually add the relevant entrypoint to your proxy for port 5432 tcp and then add a dynamic file to point to the db container:5432

making it public bypasses the proxy and directly connects the host to the container, so you would need to remove that before adding the entrypoint and port to the proxy

[noahsmiths]

Ah I see now, thank you for the explanation!