21 days ago
Hello Railway Support,
My service is healthy internally, but the public Railway edge is returning persistent HTTP 429 before requests reach the application.
Project:
adaptable-expression
Environment:
production
Service:
sayha
Public domain:
https://sayha-production.up.railway.app
Public response:
HTTP 429
server: railway-hikari
body: rate limited
Internal request from inside the Railway container:
/api/v1/health → HTTP 200
PostgreSQL, Redis, and storage are healthy.
Under Attack Mode is disabled.
Railway service metrics show no 429 responses at the application/service layer.
Traffic is low and there is no request flood.
Example headers:
x-railway-edge: bcn1
x-hikari-trace: bcn1.jwax
Browser requests from:
https://sayha-web-production.up.railway.app
are also failing because the Railway edge 429 response does not include CORS headers.
Please investigate whether there is an edge-level rate limit, abuse flag, or Hikari protection affecting this service/domain and clear it if appropriate.
1 Replies
21 days ago
The "sayha" service in your adaptable-expression project has Under Attack Mode enabled (set to on until manually disabled). This setting causes the edge to challenge or rate-limit incoming requests before they reach your application, which matches the 429 responses you are seeing. The sayha-admin service in the same project has it off, so you may have been checking that one. You can disable it from the sayha service's edge settings.
Status changed to Awaiting User Response Railway • 21 days ago
14 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 • 14 days ago