Something wrong with Public Edge
nodays-off
PROOP
a month ago
- Message: "Public edge returns zero-response timeout for all domains mapped to this service (
api-production-a156.up.railway.app,api-production-7bcf.up.railway.app, custom domainapi.jodabit.com). Container is healthy — logs show active Pub/Sub/Redis work.httpLogsGraphQL returns empty. All 3 URLs resolve to 151.101.2.15 but TCP connections never complete. Custom domainsyncStatus: ACTIVEbutDNS_RECORD_STATUS_REQUIRES_UPDATE. Started ~12h ago, persisted through multiple redeploys, healthcheck toggles, and fresh domains."
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
Railway
BOT
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
I'd make sure the port your URL is mapped to is the same port your application is listening to.