Railway CLI not working for Cursor agents
curiouskal
PROOP

a month ago

error im seeing in the cursor agent terminal instance:

$ railway logs --service medusa-WORKER --lines 300 | Select-String "MNL-CATLG-FULL"

Failed to fetch: error sending request for url (https://backboard.railway.com/graphql/v2)

Caused by:

0: error sending request for url (https://backboard.railway.com/graphql/v2)

1: client error (Connect)

2: tcp connect error: No connection could be made because the target machine actively refused it. (os error 10061)

3: No connection could be made because the target machine actively refused it. (os error 10061)

Solved

3 Replies

The error 10061 (connection actively refused) indicates the Cursor agent terminal can't establish a network connection to our API. This typically happens when the agent environment runs in a sandboxed or restricted network context that doesn't have the same outbound access as your regular terminal. Try running the same command from a standard PowerShell or terminal window outside of Cursor to confirm the CLI works normally there. If you need to diagnose network connectivity further, we have a NetDiag tool that can help identify where connections are being blocked. Unfortunately, this is a limitation of how Cursor's agent terminal handles network requests rather than something we can control on our end.


Status changed to Awaiting User Response Railway about 1 month ago


curiouskal
PROOP

a month ago

i see. thanks for the info. Im guessing this is something due to the latest update in Cursor.


Status changed to Awaiting Railway Response Railway about 1 month ago


Let us know what we can do and if we need to engage with their team.


Status changed to Awaiting User Response Railway about 1 month ago


Railway
BOT

a month 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 about 1 month ago


Loading...