Hi Railway team,

We are seeing a consistent 403 response from Meta's crawler / Facebook Sharing Debugger.

Affected URLs:

- https://photofuture.antspro.com/

- https://.up.railway.app/

Issue summary:

- The app is publicly accessible in browsers

- The page contains the required meta tags, including Meta Verification Tag.

- We added robots.txt rules explicitly allowing:

- facebookexternalhit

- Facebot

- Meta Sharing Debugger still reports HTTP 403

- The same 403 happens on both:

- our custom domain

- the Railway-provided domain

Because the Railway-provided domain also returns 403 in Meta Sharing Debugger, this appears to be happening before or at the edge layer rather than inside our application.

Business impact:

- This blocks Meta domain verification

- This prevents proper Facebook / Instagram crawler access

- This may affect Pixel/CAPI/domain-related setup and sharing/debug flows for Meta

Please investigate whether Railway edge / Fastly bot protection is blocking Meta/Facebook crawler traffic for this service, including:

- facebookexternalhit

- Facebot

- Meta crawler IP ranges or internal scraping infrastructure

Please confirm whether this traffic can be allowlisted or otherwise unblocked.

Project ID:

- db54fc3d-d601-4e8b-a61c-6740b4c13593

Railway domain:

- photofuture-production.up.railway.app

Custom domain:

- https://photofuture.antspro.com/

Thanks