well the underlying service is not found, so there's nothing to resolve. ez.

"The underlying service is valo-app in project dazzling-reflection. The service is online at valo-app-production.up.railway.app. DNS is fully propagated:

• www.appvalo.com → 68qj1y15.up.railway.app
• appvalo.com → xn8evbrz.up.railway.app

Please manually verify both domains."

I'm having the same issue. This might be effecting a handful of us, I've seen a couple of posts with similar issues

https://station.railway.com/community/dns-not-updating-on-hobby-account-f1768640

/favicon.ico:1 Failed to load resource: the server responded with a status of 404 ()

Understanding the problem:

This error occurs when the browser attempts to fetch a resource (such as an image, JavaScript file, CSS file, or API endpoint) but the server cannot find it at the specified URL. The 404 Not Found status code means the connection to the server was successful, but the specific path provided is invalid.

How to verify:

• Identify the resource: Open the Network tab in Chrome DevTools.
• Filter by status: Look for the row highlighted in red with a status of 404.
• Check the URL: Hover over the name of the failed request to see the full Request URL.
• Test manually: Copy that URL and paste it into a new browser tab. If it still shows "Not Found," the path is definitely incorrect or the file is missing from the server.

Suggested fix:

The fix depends on why the path is failing. Common solutions include:

• Fix Typos: Ensure the filename and folder names are spelled correctly.
• Check Case Sensitivity: Most web servers (Linux-based) are case-sensitive. Image.jpg is not the same as image.jpg.
• Correct Relative Paths: Ensure you are navigating directories correctly (e.g., using ../ to go up a level).
• Verify Build Process: If you are using a framework (React, Vue, etc.), ensure the file is in the public folder or is being correctly processed by your bundler.