Cloudflare 1010 blocks project-token API query from GitHub Actions
Anonymous
OP

14 days ago

Please review a Cloudflare 1010 block affecting our read-only backup automation and confirm the supported client configuration or an appropriate exception.

Time: 2026-10-29 02:25:27 UTC

Client: Python urllib, default User-Agent, GitHub-hosted Ubuntu 24.04 runner.

POST https://backboard.railway.com/graphql/v2

Headers: Content-Type: application/json; Project-Access-Token: [REDACTED]

Body: {"query":"query { projectToken { projectId environmentId } }","variables":{}}

Response: HTTP 403; "error code: 1010".

We checked the endpoint, method, JSON, header, secret injection, and whitespace handling. The dashboard shows the token scoped to production; API authentication remains unverified because this query is blocked. Full app/configuration backups cannot complete. The application remains online.

Is an application-specific User-Agent the supported configuration for this endpoint, and could it resolve this 1010 response, or does the blocking rule need review? We have not tested that change and have stopped retries.

No secrets or private repository links are included; resource IDs can be supplied privately.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway • 14 days ago


dizzydes90
EMPLOYEE

14 days ago

Error 1010 is a Cloudflare refusal based on the requesting client's signature. It doesn't mean your token, query, or project-token scope is wrong, and it doesn't on its own mean the runner's network is blocked. To reach the API, calls have to come from a client and network that pass Cloudflare's security checks.

The next step is to change the HTTP client configuration in your backup workflow or pick a different client that Cloudflare accepts. Setting an application-specific User-Agent is a reasonable first change to try, but we can't promise that any particular header value or client will be accepted. Once a request gets through, the projectToken { projectId environmentId } query you're using with the Project-Access-Token header will confirm whether the token authenticates.


Status changed to Awaiting User Response dizzydes90 • 14 days ago


Railway
BOT

7 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 • 7 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...