2 days ago
Hello,
I need help troubleshooting a custom domain for our Spring Boot backend.
The application starts successfully and listens on port 8080. The Railway-generated domain returns HTTP 200 and the expected JSON response, but the custom domain returns HTTP 404 with “Application not found”.
Service details:
Project: independent-surprise
Service: Repositorio-2026-17
Environment: production
Target port: 8080
Working endpoint:
https://repositorio-2026-17-production.up.railway.app/usuarios
Affected endpoint:
https://api.acusab.ed.cr/usuarios
Checks performed:
Railway shows both the CNAME and TXT verification records as verified.
The public CNAME for api.acusab.ed.cr resolves to oy0ho9ts.up.railway.app, matching the target displayed by Railway.
The custom domain’s target port is 8080, matching the application.
The application logs confirm successful startup and a working MySQL connection.
The custom domain response includes:
HTTP status: 404
Message: “Application not found”
Header: x-railway-fallback: true
Request ID from a failed request on September 7, 2026: 1AM_N_VOQNeJO1wewoOzXw
Could you please check whether the custom domain is correctly associated with the active deployment and help identify why it is receiving Railway’s fallback response?
I can provide screenshots of the DNS records and Railway networking settings.
Thank you for your help.
10 Replies
Status changed to Awaiting Railway Response Railway • 2 days ago
2 days ago
Your DNS and certificate are both correct, but the edge routes for api.acusab.ed.cr were never installed. We've triggered a routing repair, which should complete within a few minutes. The custom domain will begin serving traffic once the routes are in place.
Status changed to Awaiting User Response Railway • 2 days ago
brody
Your DNS and certificate are both correct, but the edge routes for `api.acusab.ed.cr` were never installed. We've triggered a routing repair, which should complete within a few minutes. The custom domain will begin serving traffic once the routes are in place.
2 days ago
Thank you for identifying the issue and initiating the routing repair. I’ll wait a few minutes and test the custom domain again. I’ll let you know if the issue persists. I appreciate your help!
Status changed to Awaiting Railway Response Railway • 1 day ago
Status changed to Awaiting User Response brody • 1 day ago
9 hours ago
Hi!
We still waiting for a solution, cause the issue is not resolve yet!
Status changed to Awaiting Railway Response Railway • about 9 hours ago
9 hours ago
Your DNS and certificate are still correct, but the edge routes for the custom domain have not yet been installed. We have re-started the routing repair, which should complete within a few minutes. Once it finishes, the custom domain will begin serving traffic from your deployment.
Status changed to Awaiting User Response brody • about 9 hours ago
Status changed to Awaiting Railway Response Railway • about 7 hours ago
acusab-it
7 hours ago
Make sure the target port for your custom domain is set to the right port
mayori
Make sure the target port for your custom domain is set to the right port
7 hours ago
Hi!
I’ve checked the custom domain’s target port, and it is set to 8080, matching the application logs: “Tomcat started on port 8080 (http)”. The Railway-generated domain also works correctly.
Status changed to Awaiting Railway Response Railway • about 7 hours ago
Status changed to Awaiting Railway Response Railway • about 6 hours ago
Status changed to Awaiting User Response Railway • about 6 hours ago
3 hours ago
We are working on a fix, but in the meantime, you can resolve this by removing and re-adding the domain. I know that isn't ideal, but it is only an interim solution. Our fix will prevent this from happening again.