9 days ago
HI Team
I have 2 domains created api.schollyapp.com and www.scholyapp.com. Both of these are working fine. Now I have created an apex domain schollyapp.com so the user get the correct page without the www. This is throwing error for me even after configuring it properly.
It shows DNS not udpated.
Can you rectify this.
Thanks.
7 Replies
9 days ago
The traffic record for schollyapp.com is pointing to Railway correctly, but the TXT ownership-verification record at _railway-verify.schollyapp.com has the wrong value - it looks like it was copied from one of your other domains. You can find the correct verification value for schollyapp.com in the domain's settings on your Railway dashboard, then update the TXT record at your registrar to match. Once it propagates, the certificate will issue automatically.
Status changed to Awaiting User Response Railway • 9 days ago
Railway
The traffic record for `schollyapp.com` is pointing to Railway correctly, but the TXT ownership-verification record at `_railway-verify.schollyapp.com` has the wrong value - it looks like it was copied from one of your other domains. You can find the correct verification value for `schollyapp.com` in the domain's settings on your Railway dashboard, then update the TXT record at your registrar to match. Once it propagates, the certificate will issue automatically.
9 days ago
its configured correctly now.
Not Found
The train has not arrived at the station.
Please check your network settings to confirm that your domain has provisioned.
If you are a visitor, please let the owner know you're stuck at the station.
Request ID:
X1JBOOtfR6izQGQy7fhULg
Status changed to Awaiting Railway Response Railway • 9 days ago
9 days ago
The TXT verification record at _railway-verify.schollyapp.com still contains the wrong value, which is why the domain is showing the "train has not arrived" page. The traffic record is correct, but the certificate cannot issue until the verification token matches. Please check the domain settings for schollyapp.com in your Railway dashboard and update the TXT record at your registrar to the exact value shown there. Once propagated, verification and the certificate will complete automatically.
Status changed to Awaiting User Response Railway • 9 days ago
9 days ago
when you say _railway-verify.schollyapp.com TXT value, I cannot do this in hostiger. When I submit this value it changes to _railway-verify and trims the schollyapp.com. This domain is configured as ALIAS in hostinger.
Status changed to Awaiting Railway Response Railway • 9 days ago
9 days ago
That trimming is normal - Hostinger automatically appends the domain, so _railway-verify in their interface is correct and already resolves as _railway-verify.schollyapp.com. The record name is fine. The issue is the record's value: it currently contains a verification token from one of your other domains. Open the domain settings for schollyapp.com in your Railway dashboard, copy the verification value shown there, and replace the current TXT record value in Hostinger with it. Once it propagates, the certificate will issue automatically.
Status changed to Awaiting User Response Railway • 9 days ago
9 days ago
it is 100% configured correctly. TXT
_railway-verify
0
"railway-verify=ff6.... "
Status changed to Awaiting Railway Response Railway • 9 days ago
9 days ago
issue resolved now.
Status changed to Solved pballa • 9 days ago