Skip to content
Deployments still blocked – "Limited Access" after security incident
laquesta
OP

a month ago

Deployments still blocked – "Limited Access" after security incident

Hi everyone,

My Railway project has been unable to deploy since October 21, following the recent security incident.

Even though Railway's status page indicates that deployments have been restored, my project still displays:

"Limited Access – Deploys have been paused temporarily"

I've already tried:

  • Reconnecting my GitHub repository.
  • Verifying GitHub permissions and automatic deployments.
  • Pushing a new commit to trigger a deployment.
  • Manually deploying through the Railway CLI.

Unfortunately, nothing works. The CLI immediately returns:

"Deploys have been paused temporarily"

My Trial account is still active, with remaining credit and time.

The service currently has no active deployment, which also prevents me from accessing the files on its persistent volume.

Is anyone else still experiencing this issue?

Does anyone know whether Railway is still restricting certain accounts or workspaces, or how to get this restriction lifted?

I've been unable to deploy for four days now, so any help would be greatly appreciated.

Thanks!

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 27 days 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


Railway
BOT

20 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 20 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...