a month ago
I've set up , my website URL on Railway but I can't view it. It has security errors and cannot be viewed - I want it to be live. What's wrong with it.
19 Replies
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
I'm new at this so what is wrong? I created the code with Claude, set up a GitHub Repository and now set it up on Railway to see on the internet with my domain name. I changed the DNS as prompted by your setup but I still cannot see the site up live using the domain name. See site in browser. MusicMovieTrivia.com
a month ago
I know - I saw that but I've setup the DNS changes on the URL. What am I missing? The Railway backend shows that the website is online.
a month ago
I'm not sure how to fix this situation. I'm new to Railway and this type of site hosting.
a month ago
Sure - Could this be something that takes time to propagate when you change from one server to another? getting screen shots
heisedesign
a month ago
Can you also get a screenshot of the service's networking section?
a month ago
Think it might be just waiting for the DNS to propagate. What do you think?
Attachments
heisedesign
Think it might be just waiting for the DNS to propagate. What do you think? 
a month ago
Hey, I believe that you have set the TXT record with the wrong hostname. The TXT record is set for musicmovietrivia.com, but should have been for _railway-verify.musicmovietrivia.com.
Additionally, can you try generating a domain and see you can access your deployment this way? Please also attach a screenshot of the Deployments panel.
a month ago
I just added that into the DNS record along with this in the answer column :
railway-verify=6b744986e3f5d6228e47bbf779a17ff487af374c47614834a2f97d5bec2b8267
600
a month ago
It seems like it should be working but I'm now getting a 502 bad gateway error in the browser.
heisedesign
It seems like it should be working but I'm now getting a 502 bad gateway error in the browser.
a month ago
Can you check the port your service is listening to (you can most likely find it in the deploy logs of your deployment)? Make sure to match the port with your custom domain.
a month ago
Still Unresolved - I need to go now thanks for the help - this is driving me nuts. Still getting no page load and error messages. Out
a month ago
Hey I can access the site. https://musicmovietrivia.com/ this is it right? try clearing your browser cache and reconnecting or connect from your phone
a month ago
Try changing the port in the network tab to something like 8080. And add this to your server.js at the end.
const PORT = process.env.PORT || 3000;
Status changed to Solved Railway • 29 days ago