Your CNAME is still pointing to the old Railway target rather than the one currently assigned to your domain. In Cloudflare, update the CNAME value to dvaywb4j.up.railway.app (visible under Service > Settings > Networking > Public Networking) and make sure the proxy is off (gray cloud). You also need a TXT record at the verification host shown on that same page for ownership verification, as the certificate will not issue until both records are in place. Once both are set, the "Waiting for DNS" state should clear.

I did, I talked to Cloudflare's bot, gave them the chat here... it did everything you said... still broken

The CNAME is still resolving to rustmcmcarps-production.up.railway.app right now, not the required dvaywb4j.up.railway.app, and no TXT verification record exists yet. In Cloudflare, delete the existing CNAME record entirely and create a new one pointing to dvaywb4j.up.railway.app with the proxy off (gray cloud), then add a TXT record at the verification host shown under Service > Settings > Networking > Public Networking with the token displayed there.

I can't even get into my project: 404

Looks like you are lost

Your project is still in your dashboard and has not been deleted. The 404 is on your service's domain because your deployments are currently stuck in the queue due to an ongoing deployment infrastructure issue, tracked at this incident page. Once deployments resume, you will still need to update your CNAME to the correct target and add the TXT verification record as described in the earlier messages for your custom domain to work.

Explain to me what you are talking about with TXT verification... I have looked all over, it's not there...

The TXT verification details are not always prominently displayed in the Networking section you screenshotted. Click the edit icon (pencil) next to your custom domain entry, and you should see the required TXT record host and value. In Cloudflare, create a TXT record using that host and value. You also still need to update the CNAME to point to dvaywb4j.up.railway.app with the proxy off (gray cloud), as it is currently pointing to the old target.

dvaywb4j.up.railway.app gives me a 404 Error, so you are incorrect

That target was for the previous domain you had configured, which has since been removed. Your current custom domain has a different assigned target, and your CNAME is already pointing to it correctly. Your service is running and responding on its Railway-generated domain. The only remaining step is to add the TXT verification record so the certificate can issue: in Cloudflare, create a TXT record with the host and value shown when you click the edit icon next to your custom domain under Service > Settings > Networking > Public Networking.

There is no TXT verification record in that setting... I went to the project, then Settings >> Network >> I see the CNAME but no details for TXT

Your CNAME is already correct and shows as propagated on our side, so leave it as it is. The dvaywb4j target was for a domain you previously had configured, not this one, so you can ignore that.

The only thing still missing is the ownership TXT record, which is why the certificate has not issued and HTTPS keeps failing. It has not been surfacing clearly in the dashboard for your domain, so here it is directly. In Cloudflare, add a TXT record with the name _railway-verify and the value railway-verify=7ada75777e6c7b137eb726aa740d4cf97891277ede030ac8086f301ca3677faf, left unproxied (DNS only, gray cloud).

Once it propagates, ownership verifies and the certificate issues on its own, and the "Waiting for DNS" state clears. Your app itself is healthy and already serving on its Railway-generated domain, so nothing else needs changing. Reply here once the TXT record is in and we will re-check verification from our side.