an hour ago
False positive workspace restriction for CC-Panel (Claude Code Control Panel) open-source dashboard
Problem and desired outcome
I am deploying a self-hosted, open-source administrative dashboard called CC-Panel (Claude Code Control Panel) from GitHub to Railway. The workspace was immediately restricted upon project creation with the notice: "We limited this workspace after detecting unusual activity. Upgrade to a paid plan to lift this restriction automatically." The project is an internal development orchestration tool and does not conduct abusive traffic, automated payment testing, port scanning, or malicious operations. I request an operational review of the repository to clear this automated heuristic flag and restore workspace deployment access.
Resources and timing
- Repository URL: https://github.com/wubaluba-dubdub/CC-Panel (Branch: mimo_v2.5)
- Railway Workspace Name / ID: [Workspace Name / ID]
- Project URL: [Project URL]
- Timestamp of restriction: 2026-11-04 UTC
Evidence and attempts
- Observed message: "We limited this workspace after detecting unusual activity. Upgrade to a paid plan to lift this restriction automatically."
- Trigger analysis: The restriction was applied automatically prior to sustained workload execution. The abbreviation "CC" stands for Claude Code (the developer tool by Anthropic), but automated security heuristics appear to have flagged CC-Panel as a false-positive indicator of a card testing utility or a Command & Control (C2) framework.
- Project Scope & Technical Details:
- Application: A single-container, self-hosted web control interface designed to orchestrate local software development projects and developer workflows.
- Stack: Node.js 22+, TypeScript, Fastify 5, React 19, SQLite (better-sqlite3), and Docker multi-stage builds.
- Current State: Implements single-admin authentication (Argon2id, mandatory TOTP), AES-256-GCM secret management, tamper-evident audit logging via HMAC chains, project workspace isolation (/data/projects/), and a chunked file manager.
- Verification: The project runs on a single origin, uses local persistent SQLite storage on /data, and contains zero payment gateway code, scraping bots, or network tunneling services.
Why contact support?
Initiated by the user. The restriction is an automated platform-level security hold triggered at repository import time. Only Railway support can inspect the workspace state, verify the benign nature of the source repository, and lift the restriction flag.
Uncertainty and constraints
- Leading hypothesis: Keyword and heuristic false positive triggered by the repository slug CC-Panel.
- Constraints: No resource modifications or external state adjustments are needed—only manual clearance of the automated workspace flag.
Prepared with Railway's support template (v1).
9 Replies
an hour ago
This restriction lifts when the workspace is upgraded to a paid plan. Upgrading to Hobby or Pro from the plans page removes it automatically. Adding a payment method on its own does not lift it.
There is no appeal or manual review for this kind of restriction, so a code review of your repository will not change it. The upgrade is the way to restore deployment access.
Status changed to Awaiting User Response Railway • about 1 hour ago
Railway
This restriction lifts when the workspace is upgraded to a paid plan. Upgrading to Hobby or Pro from the [plans page](https://railway.com/workspace/plans) removes it automatically. Adding a payment method on its own does not lift it. There is no appeal or manual review for this kind of restriction, so a code review of your repository will not change it. The upgrade is the way to restore deployment access.
an hour ago
I'm not convinced.
why my project?
what's wrong with it?
Status changed to Awaiting Railway Response Railway • about 1 hour ago
an hour ago
We understand it's frustrating to see this without an explanation. We don't share the specific signals behind this kind of limit, and it isn't lifted through a review of your repository, so we can't point to anything in CC-Panel as the cause.
Upgrading the workspace to Hobby or Pro from the plans page lifts the limit automatically and restores deployment access. Adding a card without upgrading does not lift it.
Status changed to Awaiting User Response Railway • about 1 hour ago
Railway
We understand it's frustrating to see this without an explanation. We don't share the specific signals behind this kind of limit, and it isn't lifted through a review of your repository, so we can't point to anything in CC-Panel as the cause. Upgrading the workspace to Hobby or Pro from the [plans page](https://railway.com/workspace/plans) lifts the limit automatically and restores deployment access. Adding a card without upgrading does not lift it.
an hour ago
how should I know that the problem is my account or my project?
Status changed to Awaiting Railway Response Railway • about 1 hour ago
an hour ago
The limit is on your workspace, not on CC-Panel or any single project. It applies to everything in the workspace equally, and it is the same notice you would see whatever repository you deployed.
That also means changing, renaming, or removing the project won't clear it. Upgrading the workspace to Hobby or Pro from the plans page is what lifts it.
Status changed to Awaiting User Response Railway • about 1 hour ago
Railway
The limit is on your workspace, not on CC-Panel or any single project. It applies to everything in the workspace equally, and it is the same notice you would see whatever repository you deployed. That also means changing, renaming, or removing the project won't clear it. Upgrading the workspace to Hobby or Pro from the [plans page](https://railway.com/workspace/plans) is what lifts it.
an hour ago
I mean is there a problem with my project that you limit my workspace?
Status changed to Awaiting Railway Response Railway • about 1 hour ago
an hour ago
We understand wanting a clear answer on this. We don't share what triggers this kind of limit, so we can't say whether anything about the deployment was involved. It also isn't a finding that something is wrong in CC-Panel's code, because the limit doesn't come from a review of your repository.
Upgrading the workspace to Hobby or Pro from the plans page still lifts it automatically.
Status changed to Awaiting User Response Railway • about 1 hour ago
Railway
We understand wanting a clear answer on this. We don't share what triggers this kind of limit, so we can't say whether anything about the deployment was involved. It also isn't a finding that something is wrong in CC-Panel's code, because the limit doesn't come from a review of your repository. Upgrading the workspace to Hobby or Pro from the [plans page](https://railway.com/workspace/plans) still lifts it automatically.
an hour ago
so the only way is to upgrade my account?
Status changed to Awaiting Railway Response Railway • about 1 hour ago
an hour ago
Yes, upgrading the workspace to Hobby or Pro from the plans page is the way to lift this limit, and it lifts automatically once the upgrade goes through. Adding a card without upgrading won't remove it.
Status changed to Awaiting User Response Railway • about 1 hour ago
Status changed to Solved Anonymous • about 1 hour ago