Domain Mapping leads to the wrong cloud run application

I have 2 google cloud run applications with different subdomain names (ex: abc.example and def.example). These 2 subdomains have DNS entries (CNAME records) in GoDaddy, abc and def, both pointing to ghs.googlehosted I have configured custom domains in GCP as well correctly - abc pointing to abc.example and def pointing to def.example. Now both applications are accessible correctly under their specific domains except for one scenario.

Here is the scenario:

  • When I use abc.example/login it correctly goes to the login page of the abc application

  • but when I just use abc.example (without any resource name at the end), it goes to def.example!

It sounds like your domain mappings are overlapping. In Cloud Run, each subdomain (e.g. abc.example, def.example) must have its own domain mapping — if there’s a wildcard (*.example.com) or shared SSL certificate covering both, traffic may be routed incorrectly.

Check under Cloud Run → Domain mappings and Network Services → Certificates to ensure each subdomain is mapped and certified separately. Remove any wildcard or duplicate mappings, then redeploy both services.

Thanks for the quick response. I don’t see anything called Network Services under Cloud Run → Domain Mappings. I see “Networking”, but it doesn’t have “Certificates”. It only has “Ingress”, “End Points”, “VPC” and “Service Mesh”. None of them have any setting that points to any overlap.

I figure out the issue. Sorry, the issue was on my side and nothing to do with the custom domain setup. The landing page was wrongly configured in one of the apps. I have fixed it now. Thanks for the help