23 days ago
Logs seem to show nothing, double checked code and logs and tried everything I could think of. I hosted the same code locally and the dashboard opened and loaded just fine on exactly the same code. given that the same code ran fine locally, I'm inclined to believe it's not a code issue...any guidance you can provide would be very helpful. I'd provide logs if I could to show what's wrong but everything genuinely looks OK, including build logs and deployment logs and HTTP too.
4 Replies
Status changed to Open Railway • 23 days ago
23 days ago
If I understood correctly, your app isn't accessible through the http URL? Meaning you're getting "Application failed to respond" error? In this case, you need to ensure your app is listening on the same port your URL is mapped to, in your service settings.
23 days ago
We need more info on your issue, how are you fetching the dashboard data, where is the DB hosted, have you properly configured all the needed env vars...?
23 days ago
This is the error (below). There is no data setup at the moment, but there is a populated but empty Postgres set up with a working schema, the same one that I used on my local Docker. DB is currently hosted on Railway too in the same project. Env vars to my knowledge shouldn't be needed for population of an empty no-auth dashboard at the moment. When I ran it locally yesterday, it populated properly in the browser, showing the UI and the tabs that have been built. My plan was to see the same thing here, confirming that it's up and running and deployed properly, and then populating the Railway DB with some synthetic data to then check that the DB's data were flowing through React to the dashboard properly. To darseen's point as well, I did confirm that the app is listening to the same port the URL is mapped to.
Edit: the page title when I get this error is "502 Bad Gateway". I'm not an expert by any means, so I'm not sure what exactly that implies...
Attachments
23 days ago
Fixed. I still don't know why because I changed nothing. The error went from the above to a blank page saying the following, from which I fixed in Github and redeployed and now it populates properly. (URL partially redacted of course). Easy fix, no clue why it didn't just show this from the beginning.
Blocked request. This host ("*****.up.railway.app") is not allowed. To allow this host, add "*****.up.railway.app" to preview.allowedHosts in vite.config.js.
Status changed to Solved Railway • 23 days ago