Hi Railway team,

I'm on the Hobby plan. Project: pacific-sparkle. Service: Valu8.

I've added a custom domain, www.valu8.co.uk, to my service.

The DNS is correct and verified:

• CNAME www.valu8.co.uk → vxoznjsq.up.railway.app

• Railway's dashboard shows the domain status as VALID

• DNS is fully propagated (confirmed via Google DNS 8.8.8.8)

• No CAA records are blocking issuance

The problem: Railway is not issuing a Let's Encrypt SSL certificate

for www.valu8.co.uk. Requests keep being served the default

*.up.railway.app wildcard certificate and return a 404 / privacy

error in the browser.

A second custom domain on the SAME service, valu8.buckswell.co.uk,

has a valid certificate and works perfectly, so the mechanism clearly

works in general.

When adding the domain, the dashboard showed:

"You have hit the custom domain limit for your plan. Please upgrade

to add more."

Questions:

1. Is the Hobby-plan custom-domain limit preventing the SSL

   certificate from being issued for www.valu8.co.uk?

2. If so, what do I need to do, upgrade the plan, or remove an

   existing custom domain first?

3. Can you manually trigger / force certificate provisioning for

   www.valu8.co.uk?

Thank you