24 days ago
Our production Railway service (263iptet.up.railway.app, service ID fa476daa) is returning 403 to Facebook's crawler (facebookexternalhit), but our UAT service (ysecajsp.up.railway.app, service ID 3027f3b8) works fine with Facebook. Both services run identical code. The 403 happens before reaching our Express server (no 403 in server logs). Facebook confirmed the 403 via their Sharing Debugger. We suspect Fastly CDN is blocking Facebook's crawler IPs specifically for the production service. Please investigate.
3 Replies
Status changed to Open Railway • 24 days ago
24 days ago
It is affacted at all for our Business Impact: Merchant dependence on Facebook sharing for auction promotion."
24 days ago
This is almost certainly a Fastly Bot Protection / WAF Rule. Try to allow Facebook crawler explicitly on the edge configuration.
18 days ago
We've traced this to Meta/Facebook's side. On our end, the request comes through and we respond with HTTP 200 — but Facebook's debugger reports a 403, which points to something happening after the response leaves us. Since the failure is on their end, it's not something we can fix from here. You'll want to raise this with Meta directly.
Status changed to Solved ray-chen • 18 days ago