Your CNAME record is correctly resolving to the expected Railway domain, and we can see www.rsdatourandtravels.com is configured on your service. Certificate issuance typically completes within an hour but can take up to 72 hours as noted in our SSL troubleshooting docs, so 15 minutes is still well within the normal window. Please avoid deleting and re-adding the domain, as that can trigger Let's Encrypt rate limits.

isssue with both rsda-tripmate-frontend-production-f07c.up.railway.app

demo.rsdatourandtravels.com canonical name = rsda-tripmate-frontend-production-f07c.up.railway.app.

Name: rsda-tripmate-frontend-production-f07c.up.railway.app

Address: 66.33.22.1

www.rsdatourandtravels.com canonical name = rsda-tripmate-frontend-production-4474.up.railway.app.

Name: rsda-tripmate-frontend-production-4474.up.railway.app

Address: 66.33.22.1 only seems ssl issue

not solved yet

Both custom domains have their CNAME records correctly pointing to Railway, but neither has the required _railway TXT verification record. Certificates won't issue until ownership is verified. You need to add a TXT record for each domain - the exact values are shown in your domain settings on the Railway dashboard. For www.rsdatourandtravels.com, add the TXT record at _railway.www.rsdatourandtravels.com. For demo.rsdatourandtravels.com, add it at _railway.demo.rsdatourandtravels.com. Your DNS provider appears to be GoDaddy (domaincontrol.com nameservers).

This error appears to be caused by the application.

If this is your project, check out your deploy logs to see what went wrong. Refer to our docs on Fixing Common Errors for help, or reach out over our Help Station.

If you are a visitor, please contact the application owner or try again later.

Request ID:

e28a1DaNRAOvAGeUV7rehQ

• GET / → 200
• GET /api/auth/me → 200
• GET /api/admin/vehicles → 200
• GET /api/admin/drivers → 200
• Custom domain SSL - Railway domain working

self resolve inx issue