GitHub Pages build fails with "Actor is not allowed to trigger Actions workflows"

[olddox]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

My repository is olddox/ocolor (public, personal account). I uploaded an index.html
via the web UI and enabled GitHub Pages (Settings → Pages → Deploy from a branch,
main / root).

The "pages build and deployment" workflow run fails immediately with:

Startup failure
Error: Actor is not allowed to trigger Actions workflows.

Repository Settings → Actions → General is set to "Allow all actions and reusable
workflows", so it's not a repo-level restriction. My account email is verified.

Could someone help me understand why my account/actor is blocked from triggering
Actions workflows, and how to resolve it?

Repo: https://github.com/olddox/ocolor

[AryanSinghh07]

Hey Owen, I ran into something similar a while back — this isn't a repo-level setting, it's an account-level restriction GitHub applies to newer or unverified accounts as an anti-abuse measure. They've had issues with people spinning up throwaway accounts to run crypto-mining or spam workflows on free compute, so new accounts sometimes get a temporary hold on Actions.

A couple things worth checking:

1. Add and verify a phone number — go to Settings → Password and authentication and check under two-factor/verification. This is the fastest way I've seen people clear this restriction.
2. Give the account a little time — if it's very new, GitHub's automated review sometimes lifts the block on its own within a day or two, no action needed.
3. If it's still blocked after that, it's worth opening a ticket with GitHub Support directly (not something fixable from repo settings) — there's a discussion where someone confirmed this is exactly the kind of temporary account-level hold Support has to manually clear: https://github.com/orgs/community/discussions/189338

Since your repo-level Actions permissions are already set correctly ("Allow all actions and reusable workflows"), that rules out the usual repo-config culprit — which is what points this toward an account-level thing rather than something in your olddox/ocolor settings.

[pira73br]

Adding a bit of context specific to your setup (Deploy from a branch on main / root for olddox/ocolor):

What’s going on

Error: Actor is not allowed to trigger Actions workflows is usually an account-level Actions hold (anti-abuse), not a bad Pages/repo toggle. That’s why Settings → Actions → Allow all actions… already being correct doesn’t fix it.

GitHub Pages “Deploy from a branch” still uses the pages build and deployment Actions workflow behind the scenes, so if your account can’t trigger Actions, Pages fails immediately and you get a 404.

What to try

1. Verify phone / strengthen account verification
   Settings → Password and authentication (phone / 2FA). This is the most common unlock.
2. Wait 24–48h if the account is new
   Automated review sometimes lifts the hold by itself.
3. Contact GitHub Support
   If it persists, only Support can clear an account-level Actions restriction. Repo settings won’t.
4. After the hold is lifted
   Re-run the failed pages build and deployment workflow, or push a tiny commit to main to retrigger Pages.

Related discussion confirming the account-hold pattern:
https://github.com/orgs/community/discussions/189338

If this helps, please mark an answer as accepted.