Your domain rproc-be-production.up.railway.app does resolve in public DNS, so this is not a DNS resolution failure. The likely cause is the private networking migration: services created before the migration require Private Networking to be enabled for public domain routing to work. In your service's Settings under Networking, enable Private Networking and redeploy.

Private Networking is already enabled

Not quite sure what DNS issues you're facing here. As mentioned above, the domain you provided is publicly resolvable.

Your backend application received the request, but you do not have a specific route configured to handle a GET request at the root URL path (/). To resolve this, you need to test an endpoint that actually exists in your application, or you need to add a default handler for the root path. If you are using Express.js, this code shows how to add a basic route handler looks like so it returns a success message instead of a 404.

const express = require('express');

const app = express();

// Add this route to handle requests to the root URL "/"

app.get('/', (req, res) => {

res.status(200).json({

status: "success",

message: "The API is up and running" 

});

});

// Define your other API routes here...

// app.use('/api', apiRouter);

const PORT = process.env.PORT || 3000;

app.listen(PORT, () => {

console.log(Server is running on port ${PORT});

});