a month ago
My workspace has been stuck on "Limited Access – Deploys have been paused temporarily" since the October 21 security incident. The status page says builds are back for all plans (including Free/Trial) as of Oct 22, but mine are still paused. I have 20 days of credit left, so it's not a usage limit.
What I've already done:
- Rotated all environment variables (new Supabase keys, DB password, Resend, EasyPost) per your security notice
- Signed out and back in, hard refreshed
- Reconnected GitHub
- Pushed a new commit (43ad20f) to main — no new deployment appears
Impact: my production site (blackmarkit.us.com) is down. It's still running a build from before the incident, which has the old, now-revoked keys baked in, so every page shows an error. I can't deploy the fix because deploys are paused.
Could you please lift the deploy pause on my workspace? Screenshot of the banner attached.
Thank you!
4 Replies
Status changed to Awaiting Railway Response Railway • 27 days ago
a month ago
Same I have the same issue, you should maybe try to email them and see if you get a reply.
a month ago
Sorry for the trouble getting deploys moving again. New deployments are being accepted on every plan.
Commits pushed while deploys were paused were not queued, so your service needs a manual deploy. Open the Command Palette (Cmd/Ctrl + K) and run Deploy Latest Commit. If that fails, reconnect GitHub in Account Settings. If you deploy from the CLI or CI, run railway logout then railway login, or create a new token, since earlier sessions and tokens were revoked. Full steps are in our recovery guide.
If the Limited Access banner is still there after a fresh attempt, reply with your project ID and the failed deployment ID and we'll look at it directly.
Status changed to Awaiting User Response Railway • 27 days ago
angelo-railway
Sorry for the trouble getting deploys moving again. New deployments are being accepted on every plan. Commits pushed while deploys were paused were not queued, so your service needs a manual deploy. Open the Command Palette (Cmd/Ctrl + K) and run Deploy Latest Commit. If that fails, reconnect GitHub in Account Settings. If you deploy from the CLI or CI, run `railway logout` then `railway login`, or create a new token, since earlier sessions and tokens were revoked. Full steps are in our [recovery guide](https://blog.railway.com/p/security-disclosure-recommendation-recover-failing-deploys). If the Limited Access banner is still there after a fresh attempt, reply with your project ID and the failed deployment ID and we'll look at it directly.
a month ago
Fixed, thanks!
Status changed to Awaiting Railway Response Railway • 26 days ago
Status changed to Solved Railway • 26 days ago
yerinsongg
Same I have the same issue, you should maybe try to email them and see if you get a reply.
a month ago
Check thier reply to me, maybe it will help, it fixed my issue.
Status changed to Awaiting Railway Response Railway • 26 days ago
Status changed to Solved Railway • 26 days ago