a month ago
Custom domain shows attached/verified in the dashboard, cert issues correctly and matches the domain (not a wildcard/fallback cert), DNS is correct and matches a working sibling subdomain's pattern.
Tried redeploy - doesn't clear it. Requests return x-railway-fallback: true / 502 "Application failed to respond."
Checked the community bounty board too: found one specific, plausibly related report — "Edge IP 69.46.46.41 appears to be blackholing all traffic (sfo) — hostname pinned to it is unreachable" (station.railway.com/bounties, 21 days old).
My custom domain currently resolves to 69.46.46.86 — same /24 subnet, same general shape (hostname pinned to a specific edge IP, unreachable despite the container being healthy).
1 Replies
a month ago
The custom domain on your listmonk service has its target port explicitly set to 9000, but the edge logs show "connection refused" on every attempt to that port, while the service domain (using auto-detect) returns 200. The app is listening on a different port than 9000. To fix this, open that custom domain's settings and either set the target port to match the port listmonk is actually binding to, or clear the explicit value so it uses auto-detect like the service domain.
Status changed to Awaiting User Response Railway • 27 days ago
19 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 19 days ago