2 months ago
My Railway service (mythly-server, production environment, region us-west1) is running healthy — the internal health check passes and logs show 200 OK: GET - /health. However, the public domain mythly-server-production.up.railway.app returns "host not found" / DNS resolution failure from all external
networks including mobile data (different ISP).
What happened before this:
The service had 3-4 consecutive failed deployments (startup crashes due to a Flyway migration bug). Each deployment crashed before the health check passed. After fixing the bug, the latest deployment started successfully and the health check passed — but the public URL never became reachable again.
Logs confirm:
Starting Container
2026-03-14 11:57:15.085 [main] INFO o.f.c.i.r.ResourceNameValidator - Set 'validateMigrationNaming' to true to fail fast and see a list of the invalid file names.
2026-03-14 11:57:14.656 [main] INFO Application - Autoreload is disabled because the development mode is off.
2026-03-14 11:57:14.811 [main] INFO Application - === Mythly Server Starting ===
2026-03-14 11:57:14.811 [main] INFO Application - PORT=8080
2026-03-14 11:57:14.812 [main] INFO Application - DEV_MODE=false
2026-03-14 11:57:14.812 [main] INFO Application - RAILWAY_STATIC_URL=mythly.up.railway.app
2026-03-14 11:57:14.812 [main] INFO Application - DATABASE_URL=jdbc:postgresql://postgres.railway.internal:5432/railway
2026-03-14 11:57:14.812 [main] INFO Application - CORS_ALLOWED_HOSTS=https://mythly-stories.vercel.app
2026-03-14 11:57:14.812 [main] INFO Application - RAILWAY_SERVICE_NAME=mythly-server
2026-03-14 11:57:14.812 [main] INFO Application - RAILWAY_PUBLIC_DOMAIN=mythly.up.railway.app
2026-03-14 11:57:14.812 [main] INFO Application - RAILWAY_ENVIRONMENT_NAME=production
2026-03-14 11:57:14.812 [main] INFO Application - Initializing database...
2026-03-14 11:57:15.084 [main] INFO o.f.c.i.r.ResourceNameValidator - 1 SQL migrations were detected but not run because they did not follow the filename convention.
2026-03-14 11:57:15.714 [main] INFO org.flywaydb.core.FlywayExecutor - Database: jdbc:postgresql://postgres.railway.internal:5432/railway (PostgreSQL 17.7)
2026-03-14 11:57:15.760 [main] WARN o.f.c.i.database.base.Database - Flyway upgrade recommended: PostgreSQL 17.7 is newer than this version of Flyway and support has not been tested. The latest supported version of PostgreSQL is 16.
2026-03-14 11:57:15.850 [main] INFO o.f.core.internal.command.DbValidate - Successfully validated 1 migration (execution time 00:00.036s)
2026-03-14 11:57:16.003 [main] INFO o.f.core.internal.command.DbMigrate - Current version of schema "public": 1
2026-03-14 11:57:16.057 [main] INFO o.f.core.internal.command.DbMigrate - Schema "public" is up to date. No migration necessary.
2026-03-14 11:57:16.113 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2026-03-14 11:57:16.279 [main] INFO com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.postgresql.jdbc.PgConnection@48976e6d
2026-03-14 11:57:16.281 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2026-03-14 11:57:16.690 [main] INFO Application - Initializing R2 storage client...
2026-03-14 11:57:16.996 [main] INFO Application - R2_PUBLIC_URL=https://pub-1c12ab428ff44219adbcedadd5ce3cd2.r2.dev
2026-03-14 11:57:16.997 [main] INFO Application - === Mythly Server Started — routes registering ===
2026-03-14 11:57:17.086 [main] INFO Application - Application started in 2.631 seconds.
2026-03-14 11:57:17.392 [DefaultDispatcher-worker-1] INFO Application - Responding at http://0.0.0.0:8080
2026-03-14 11:57:17.760 [eventLoopGroupProxy-4-1] INFO Application - 200 OK: GET - /health in 85ms
What I've tried:
- Redeployed multiple times
- Flushed DNS cache on local machine
- Tested from mobile data (different ISP)
- Deleted and regenerated the public domain
Expected: Public domain resolves and routes to the container.
Actual: DNS lookup fails entirely on all networks.
Pinned Solution
2 months ago
the domain is actually working, i just tested mythly.up.railway.app/health and got {"status":"ok"} myself. your device/isp dns just hasn't propagated the new record yet since you recreated the domain recently. try switching to google dns (8.8.8.8) on your phone temporarily or just wait 10-30 minutes and it'll resolve on its own
11 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
in your logs , your RAILWAY_PUBLIC_DOMAIN env var is set to mythly.up.railway.app but the url you're testing is mythly-server-production.up.railway.app. those are two different domains. can you check in your service settings under public networking which domain is actually listed there? that might be the whole issue right there
ilyass012
in your logs , your RAILWAY\_PUBLIC\_DOMAIN env var is set to [mythly.up.railway.app](http://mythly.up.railway.app) but the url you're testing is [mythly-server-production.up.railway.app](http://mythly-server-production.up.railway.app). those are two different domains. can you check in your service settings under public networking which domain is actually listed there? that might be the whole issue right there
2 months ago
My bad the log was of old url so mythly.up.railway.app is my current one so I was getting this error so what I did was i deleted that old url and created new but same issue
palankibharat
My bad the log was of old url so [mythly.up.railway.app](http://mythly.up.railway.app) is my current one so I was getting this error so what I did was i deleted that old url and created new but same issue
2 months ago
When you re-added the domain, what port did railway set as the target? can you confirm it shows 8080 in the public networking settings?
ilyass012
When you re-added the domain, what port did railway set as the target? can you confirm it shows 8080 in the public networking settings?
2 months ago
2026-03-14T12:17:24.545838080Z [inf] Starting Container
2026-03-14T12:17:25.910934144Z [inf] 2026-03-14 12:17:25.743 [main] INFO org.flywaydb.core.FlywayExecutor - Database: jdbc:postgresql://postgres.railway.internal:5432/railway (PostgreSQL 17.7)
2026-03-14T12:17:25.910934551Z [inf] 2026-03-14 12:17:24.932 [main] INFO Application - PORT=8080
2026-03-14T12:17:25.910942071Z [inf] 2026-03-14 12:17:24.932 [main] INFO Application - DEV_MODE=false
2026-03-14T12:17:25.910947370Z [inf] 2026-03-14 12:17:24.932 [main] INFO Application - DATABASE_URL=jdbc:postgresql://postgres.railway.internal:5432/railway
2026-03-14T12:17:25.910953681Z [inf] 2026-03-14 12:17:24.933 [main] INFO Application - CORS_ALLOWED_HOSTS=https://mythly-stories.vercel.app
2026-03-14T12:17:25.910955533Z [inf] 2026-03-14 12:17:24.804 [main] INFO Application - Autoreload is disabled because the development mode is off.
2026-03-14T12:17:25.910959837Z [inf] 2026-03-14 12:17:25.134 [main] INFO o.f.c.i.r.ResourceNameValidator - 1 SQL migrations were detected but not run because they did not follow the filename convention.
2026-03-14T12:17:25.910963136Z [inf] 2026-03-14 12:17:24.933 [main] INFO Application - RAILWAY_PUBLIC_DOMAIN=mythly.up.railway.app
2026-03-14T12:17:25.910965606Z [inf] 2026-03-14 12:17:25.134 [main] INFO o.f.c.i.r.ResourceNameValidator - Set 'validateMigrationNaming' to true to fail fast and see a list of the invalid file names.
2026-03-14T12:17:25.910969361Z [inf] 2026-03-14 12:17:24.933 [main] INFO Application - RAILWAY_SERVICE_NAME=mythly-server
2026-03-14T12:17:25.910970084Z [inf] 2026-03-14 12:17:24.931 [main] INFO Application - === Mythly Server Starting ===
2026-03-14T12:17:25.910974285Z [inf] 2026-03-14 12:17:24.933 [main] INFO Application - RAILWAY_STATIC_URL=mythly.up.railway.app
2026-03-14T12:17:25.910980631Z [inf] 2026-03-14 12:17:24.933 [main] INFO Application - RAILWAY_ENVIRONMENT_NAME=production
2026-03-14T12:17:25.910985176Z [inf] 2026-03-14 12:17:24.933 [main] INFO Application - Initializing database...
2026-03-14T12:17:25.911315393Z [inf] 2026-03-14 12:17:25.830 [main] INFO o.f.core.internal.command.DbValidate - Successfully validated 1 migration (execution time 00:00.053s)
2026-03-14T12:17:25.911335278Z [inf] 2026-03-14 12:17:25.768 [main] WARN o.f.c.i.database.base.Database - Flyway upgrade recommended: PostgreSQL 17.7 is newer than this version of Flyway and support has not been tested. The latest supported version of PostgreSQL is 16.
2026-03-14T12:17:25.942739439Z [inf] 2026-03-14 12:17:25.938 [main] INFO o.f.core.internal.command.DbMigrate - Current version of schema "public": 1
2026-03-14T12:17:25.944198590Z [inf] 2026-03-14 12:17:25.943 [main] INFO o.f.core.internal.command.DbMigrate - Schema "public" is up to date. No migration necessary.
2026-03-14T12:17:26.026263362Z [inf] 2026-03-14 12:17:26.025 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2026-03-14T12:17:26.133078238Z [inf] 2026-03-14 12:17:26.128 [main] INFO com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.postgresql.jdbc.PgConnection@48976e6d
2026-03-14T12:17:26.133081895Z [inf] 2026-03-14 12:17:26.129 [main] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2026-03-14T12:17:26.445637133Z [inf] 2026-03-14 12:17:26.444 [main] INFO Application - Initializing R2 storage client...
2026-03-14T12:17:26.537329592Z [inf] 2026-03-14 12:17:26.536 [main] INFO Application - R2_PUBLIC_URL=https://pub-1c12ab428ff44219adbcedadd5ce3cd2.r2.dev
2026-03-14T12:17:26.539052793Z [inf] 2026-03-14 12:17:26.537 [main] INFO Application - === Mythly Server Started — routes registering ===
2026-03-14T12:17:26.564566411Z [inf] 2026-03-14 12:17:26.563 [main] INFO Application - Application started in 1.89 seconds.
2026-03-14T12:17:26.904872146Z [inf] 2026-03-14 12:17:26.816 [DefaultDispatcher-worker-1] INFO Application - Responding at http://0.0.0.0:8080
2026-03-14T12:17:27.913726178Z [inf] 2026-03-14 12:17:27.911 [eventLoopGroupProxy-4-1] INFO Application - 200 OK: GET - /health in 64ms
2026-03-14T14:08:16.057625271Z [inf] 2026-03-14 14:08:15.156 [eventLoopGroupProxy-4-2] INFO Application - 404 Not Found: GET - / in 2ms
2026-03-14T14:08:22.759178170Z [inf] 2026-03-14 14:08:22.758 [eventLoopGroupProxy-4-3] INFO Application - 404 Not Found: GET - / in 3ms
2026-03-14T14:08:42.757044179Z [inf] 2026-03-14 14:08:39.179 [eventLoopGroupProxy-4-4] INFO Application - 404 Not Found: GET - / in 2ms
New logs
And yes port is 8080
2 months ago
good news, your domain is actually working now. look at your new logs , you have 404 not found: get - / at 14:08, that means traffic is reaching your container. you're getting 404 because there's no route defined at / in your app, but that's expected. try hitting mythly.up.railway.app/health and you should get 200 ok
ilyass012
your service is fully working now
2 months ago
What then how am I still not able to access it
Attachments
2 months ago
the domain is actually working, i just tested mythly.up.railway.app/health and got {"status":"ok"} myself. your device/isp dns just hasn't propagated the new record yet since you recreated the domain recently. try switching to google dns (8.8.8.8) on your phone temporarily or just wait 10-30 minutes and it'll resolve on its own
ilyass012
the domain is actually working, i just tested [mythly.up.railway.app/health](http://mythly.up.railway.app/health) and got {"status":"ok"} myself. your device/isp dns just hasn't propagated the new record yet since you recreated the domain recently. try switching to google dns (8.8.8.8) on your phone temporarily or just wait 10-30 minutes and it'll resolve on its own
2 months ago
Thankyou 🤟
palankibharat
Thankyou 🤟
2 months ago
your welcome
Status changed to Solved brody • 2 months ago