6 hours ago
Hello Railway Trust & Safety,
I believe the restriction on my workspace may have been applied in error. The project is Moments, a private media library with a web service and an automation runner. Users submit media URLs for their own library; the runner processes those jobs with fixed tools such as yt-dlp, aria2, and ffmpeg, then uploads the files encrypted. It does not execute user supplied shell scripts.
During recent troubleshooting, the runner repeatedly restarted when progress updates failed during direct media downloads. That may have caused unusual outbound requests, but it was unintended. I’ve prepared a fix to throttle those updates and route YouTube downloads through Google Colab, but I have not deployed the Railway changes while the restriction is active.
Please review the activity that triggered the restriction and let me know the specific concern. I’ll keep the Railway services stopped until the review is complete and follow any remediation steps you provide. I’m happy to share relevant logs or configuration details without sending credentials or users’ cookie data.
Thank you.
1 Replies
6 hours ago
We can't go into the specifics of a restriction in a support thread, and nothing posted here reaches the people who review it. To have the restriction on your workspace reconsidered, submit an appeal from the restriction's page under Workspace Settings, Standing (railway.com/workspace/restrictions). That opens a dedicated appeal thread, and the decision is emailed to you there.
Your explanation of the runner and the fix you've prepared belongs in that appeal. Each restriction gets one appeal, so include everything you want considered when you submit it.
Status changed to Awaiting User Response Railway • about 6 hours ago