a month ago
Hello Railway team,
I’m requesting a review of the ToS restriction on my workspace.
During development of a personal reading application, an automated coding assistant attempted to create a FlareSolverr service using:
ghcr.io/flaresolverr/flaresolverr:v3.5.0
I did not realize that deploying this image could violate Railway’s Acceptable Use Policy. The deployment was rejected before initialization: no replica started, the service never ran, and it never processed any requests. I have now permanently deleted the failed service.
The project’s intended service is a Go-based, read-only content provider API. It is not an open proxy, and the application no longer uses or requires FlareSolverr or any other challenge-bypass service. I have reviewed the Acceptable Use Policy and will not deploy this type of software again.
Relevant details:
Workspace: codel projects
Project: luma-reader-providers
Project ID: cabf9de1-c37f-4811-b7cb-9f736c0203cb
Environment: production
Failed deployment ID: 47dccee6-0ed0-40b8-a3ad-09601953f2b2
Failed deployment time: 2026-07-21 15:29 UTC
Could you please manually review the restriction and restore the workspace if possible?
Thank you.
3 Replies
a month ago
Your workspace is currently under an active restriction, and unfortunately we're not able to share the specific reason behind it or reverse it for paid-plan workspaces. We understand this is frustrating, and we're sorry for the inconvenience. If you'd like to wrap up, you can cancel your plan from your workspace billing page.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Your workspace is currently under an active restriction, and unfortunately we're not able to share the specific reason behind it or reverse it for paid-plan workspaces. We understand this is frustrating, and we're sorry for the inconvenience. If you'd like to wrap up, you can cancel your plan from [your workspace billing page](https://railway.com/workspace/billing).
a month ago
I still need help and would like this escalated to a Railway employee for manual review.
The restriction appears to have been triggered automatically when a single FlareSolverr container was created. That deployment was blocked before initialization, never ran, and never processed traffic. The service has since been permanently deleted.
I understand why the image may have triggered an automated safeguard, but no prohibited service was actually operated. Please review the deployment history and workspace restriction rather than closing this based on the automated response.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We understand this is frustrating, and we're sorry for the inconvenience. If you'd like to wrap up, you can cancel your plan from your workspace billing page.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Closed brody • about 1 month ago